#archiveteam-bs 2016-06-04,Sat

↑back Search

Time Nickname Message
00:02 πŸ”— tfgbd_znc has joined #archiveteam-bs
00:03 πŸ”— tfgbd_znc has quit IRC (Client Quit)
00:05 πŸ”— tfgbd_znc has joined #archiveteam-bs
00:07 πŸ”— tomwsmf-a has quit IRC (Ping timeout: 258 seconds)
00:08 πŸ”— tomwsmf-a has joined #archiveteam-bs
00:15 πŸ”— tfgbd_znc has quit IRC (Ping timeout: 633 seconds)
00:18 πŸ”— tomwsmf-a has quit IRC (Ping timeout: 258 seconds)
00:19 πŸ”— tomwsmf-a has joined #archiveteam-bs
00:26 πŸ”— tomwsmf-a has quit IRC (Ping timeout: 258 seconds)
00:47 πŸ”— BlueMaxim has joined #archiveteam-bs
00:50 πŸ”— nickname_ has joined #archiveteam-bs
01:00 πŸ”— nickname_ has quit IRC (Read error: Connection reset by peer)
01:08 πŸ”— schbirid has quit IRC (Ping timeout: 258 seconds)
01:20 πŸ”— schbirid has joined #archiveteam-bs
01:35 πŸ”— tfgbd_znc has joined #archiveteam-bs
02:28 πŸ”— SN4T14 Tumblr dump probably just went public: https://mega.nz/#!V9ZmSCCS!lRgT4irycFEefJvWVm0-xZOuhNRZP7Hg41rJJuydSQY
02:28 πŸ”— SN4T14 Grabbing right now, going to verify and then throw up on IA
02:54 πŸ”— SN4T14 Looks like line 3 got corrupted somewhere along the way, seems fine otherwise, and the data seems to be real, so I'm uploading it
02:55 πŸ”— yipdw is that the password leak
02:55 πŸ”— yipdw if so, why are you being a dick
03:03 πŸ”— yipdw to elaborate: there is a difference between cultural artifacts and authentication credentials. letting people check if they've suffered leaks via something like ihavebeenpwned is probably a good idea. enabling the spread of the leak, well, I'm curious to hear the rationale for that one
03:03 πŸ”— yipdw (and Troy Hunt already has the data in ihavebeenpwned, so)
03:05 πŸ”— ranma ugh, would have grabbed if less than half a gig
03:11 πŸ”— Start has quit IRC (Ping timeout: 260 seconds)
03:13 πŸ”— Frogging yipdw: yeah? I don't see it in there https://haveibeenpwned.com/PwnedWebsites
03:13 πŸ”— Frogging I see a tumblr breach from 2013
03:14 πŸ”— yipdw that's what I'm asking about
03:14 πŸ”— yipdw there was a 2013 data breach that was made public May 30
03:14 πŸ”— Frogging oh I see
03:14 πŸ”— yipdw of this year
03:14 πŸ”— Frogging ah that was my confusion then. I didn't realize the data breach was that long ago
03:14 πŸ”— Frogging I wonder where it sat around for 3 years
03:15 πŸ”— yipdw probably with people who knew the value of STFU
03:16 πŸ”— Frogging SHA1
03:16 πŸ”— Frogging oh dear
03:16 πŸ”— murk I've always wondered what happens to the other data in these breaches, it's not like people would break into sites and see the only value as being the list of username and password hashes.
03:16 πŸ”— murk is it just too big for anybody to attempt to steal and this is the only thing that makes economic sense?
03:17 πŸ”— yipdw dunno
03:17 πŸ”— yipdw though I have a theory that one of the motivations is "teach those silly tumblr users a lesson"
03:17 πŸ”— * yipdw does not have a Tumblr account
03:17 πŸ”— Frogging I do but I made it after 2013
03:18 πŸ”— murk yipdw: if that were the case it would have been made public 3 years ago.
03:18 πŸ”— yipdw maybe
03:18 πŸ”— yipdw anyway, I'd really like to know the reason to upload something like this to IA, because if there isn't one I'm just going to ask it be darked ASAP
03:19 πŸ”— Start has joined #archiveteam-bs
03:19 πŸ”— murk IA definitely has no reason to be hosting this.
03:19 πŸ”— Frogging ^
03:20 πŸ”— Frogging lol fur affinity is considered a "sensitive breach" on HIBP
03:21 πŸ”— yipdw makes sense
03:21 πŸ”— MrRadar The full source code of their site leaked due to ImageTragick and apparently their DB was partly wiped
03:21 πŸ”— Frogging idk, it's not technically a dodgy site
03:21 πŸ”— joepie91 not sure how this is different from any other leaked data?
03:21 πŸ”— joepie91 especially given that the risk involved in a credential leak very rapidly goes down
03:21 πŸ”— joepie91 once it starts becoming semi-public
03:21 πŸ”— Frogging what's the historical value of it thought joepie91
03:22 πŸ”— joepie91 (that is, people have pillaged it for all the interesting stuff already)
03:22 πŸ”— Frogging though*
03:22 πŸ”— joepie91 Frogging: that's the same question you could ask about all the other content on IA, and I'm not seeing why we should be asking it about this particular thing if the approach has always been "archive now, ask questions later"
03:22 πŸ”— MrRadar It could be interesting to see the form of a website data leak, but even then the IA should not be hosting it in a public manner right now
03:23 πŸ”— Frogging I guess I'm not in a position to argue since I'm actually downloading it and I don't even know why. I don't have any intention of actually opening it
03:23 πŸ”— ranma well, space might be saved 7zipping it
03:23 πŸ”— yipdw I'm not sure if it is different, although other leaks tend to sensitive information redacted before they're published (even if the redaction sucks), and this is pretty much all sensitive information
03:23 πŸ”— yipdw +have
03:23 πŸ”— joepie91 yipdw: it isn't anymore, really
03:23 πŸ”— joepie91 it's been sold for a while now
03:23 πŸ”— joepie91 the usefulness from a malicious perspective has pretty much disappeared
03:24 πŸ”— ranma i think there's still malicious use available
03:24 πŸ”— joepie91 hell, chances are that the teamviewer drama was the last-ditch effort to get some use out of it before it went public
03:24 πŸ”— joepie91 ranma: such as?
03:25 πŸ”— ranma one on one targeted abuse
03:25 πŸ”— yipdw joepie91: one of my issues goes something like -- out of 65 million accounts, there are going to be some that have not changed their credentials since then, and we don't know why
03:25 πŸ”— MrRadar Unless a) Tumblr has required users to change their passwords since the leak and b) those users never re-used their Tumblr password on other sites I'd say it's definitely still a risk leaking this info
03:25 πŸ”— yipdw maybe the owner of that Tumblr is dead
03:25 πŸ”— MrRadar Especially if it contains links between the user's account and the e-mail it was registered with (does Tumblr require that?)
03:25 πŸ”— ranma because of password reuse
03:26 πŸ”— Frogging MrRadar: you log in with your email address
03:26 πŸ”— MrRadar OK, so they definitely do
03:26 πŸ”— Frogging fortunately it doesn't have the yahoo "give us your cellphone" cancer
03:26 πŸ”— MrRadar (I don't have a Tumblr account, if that wasn't obvious)
03:27 πŸ”— joepie91 see above. it is essentially already public, it is unlikely that there are any valuable reused passwords that haven't already been exploited by those who have been privately circulating the dump for the past few weeks.
03:27 πŸ”— yipdw joepie91: in any case, I agree that for active accounts there is probably little risk of this information being made available on a wider scale. however I disagree that an old credential has no malicious capability
03:28 πŸ”— yipdw even if you factor out the password-username-linking-problem
03:28 πŸ”— ranma it DOES seem useful for those analysing password use
03:28 πŸ”— ranma white hat/curiosity
03:30 πŸ”— murk the black/white hat usage of that data seems to be trending towards dark at the moment.
03:30 πŸ”— ranma speaking of illegal-in-some-countries use, i wonder if any FOSS people/groups/communities are collecting bluray encryption keys
03:31 πŸ”— ranma considering AnyDVD HD's successor is requiring rebuying licenses
03:32 πŸ”— ranma oh, has anyone backed up the doom9 messageboard?
03:32 πŸ”— MrRadar That one's tricky because by default it only shows you the threads active in the last 30 days
03:33 πŸ”— MrRadar Ah, it has an "archive" link that links them all
03:33 πŸ”— ranma &daysprune=-1
03:33 πŸ”— ranma nice
03:33 πŸ”— yipdw Frogging: one good reason to make the FurAffinity breach is that, for some people, being a furry or participating in furry society is not something they want to share publicly
03:33 πŸ”— yipdw I've seen friendships wrecked over it
03:34 πŸ”— yipdw you can argue it wasn't a friendship etc etc but I think that's aside the point
03:34 πŸ”— yipdw er, make the breach SENSITIVE
03:34 πŸ”— yipdw holy fuck is my keyboard dropping words now or am I just seeing things that I didn't write
03:34 πŸ”— Frogging yeah, I think you're right
03:36 πŸ”— yipdw there's a secondary argument that someone should practice compartmentalization with credentials, but I think it's a bit much to expect someone to learn tradecraft just to explore a different facet of themselves
03:37 πŸ”— ranma the fine line of expectation of privacy/data security
03:37 πŸ”— ranma but also being responsible for putting that information out there
03:38 πŸ”— * yipdw shrugs
03:38 πŸ”— yipdw I guess I'm on the "if you're not breaking laws you really shouldn't _need_ to practice opsec" side
03:38 πŸ”— tomwsmf-a has joined #archiveteam-bs
03:38 πŸ”— yipdw I mean if you want to, fantastic
03:40 πŸ”— ranma http://www.furaffinity.net/tos
03:40 πŸ”— yipdw unfortunately there's all sorts of extralegal reasons and it's easier than ever to associate identities, so I guess I've become less sympathetic with the personal-responsibility angle
03:41 πŸ”— ranma i wonder if they used to imply privacy/discression
03:42 πŸ”— ranma too lazy to research
03:57 πŸ”— murk it's basically implied.
03:57 πŸ”— bwn has quit IRC (Read error: Operation timed out)
03:58 πŸ”— murk if people are using pseudonyms on furaffinity it's fairly obvious they are seeking non-association.
04:05 πŸ”— tomwsmf-a has quit IRC (Read error: Operation timed out)
04:07 πŸ”— tfgbd_znc has quit IRC (Ping timeout: 633 seconds)
04:20 πŸ”— Sk1d has joined #archiveteam-bs
04:20 πŸ”— Sk1d has quit IRC (Connection closed)
04:22 πŸ”— Stilett0 has quit IRC (Read error: Connection reset by peer)
04:28 πŸ”— tfgbd_znc has joined #archiveteam-bs
04:51 πŸ”— tfgbd_znc has quit IRC (Read error: Connection reset by peer)
05:14 πŸ”— dashcloud has quit IRC (Read error: Operation timed out)
05:17 πŸ”— dashcloud has joined #archiveteam-bs
05:18 πŸ”— Stiletto has joined #archiveteam-bs
05:19 πŸ”— Stiletto is now known as Stilett0
05:19 πŸ”— Stilett0 has quit IRC (Client Quit)
05:21 πŸ”— Stiletto has joined #archiveteam-bs
05:50 πŸ”— JesseW has joined #archiveteam-bs
06:42 πŸ”— dashcloud has quit IRC (Read error: Operation timed out)
06:45 πŸ”— dashcloud has joined #archiveteam-bs
06:47 πŸ”— vitzli has joined #archiveteam-bs
06:47 πŸ”— vitzli I'm getting 403 on zippcast grab - are there any geo-restrictions?
06:52 πŸ”— ndiddy has quit IRC (Read error: Connection reset by peer)
06:53 πŸ”— ndiddy has joined #archiveteam-bs
06:55 πŸ”— JesseW has quit IRC (Ping timeout: 370 seconds)
07:03 πŸ”— bwn has joined #archiveteam-bs
08:21 πŸ”— dan- has quit IRC (Ping timeout: 260 seconds)
08:25 πŸ”— Sk1d has joined #archiveteam-bs
08:29 πŸ”— Sk1d has quit IRC (Ping timeout: 194 seconds)
08:34 πŸ”— dan- has joined #archiveteam-bs
08:46 πŸ”— dan- has quit IRC (Ping timeout: 260 seconds)
08:49 πŸ”— purplebot has joined #archiveteam-bs
08:51 πŸ”— PurpleSym Just ban the bot if that gets too annoying.
08:52 πŸ”— yipdw it could have its own channel
08:53 πŸ”— will Just a note, the green highlight makes the text impossible to read on a black background
08:53 πŸ”— will Well the text is unreadable basically with that bot
08:53 πŸ”— PurpleSym I can remove colors.
08:54 πŸ”— Sanqui I approve of the bot
08:55 πŸ”— PurpleSym Wrt separate channel: I think Sanqui’s idea was to β€œconnect” wiki and IRC.
08:55 πŸ”— Sanqui Keep the colors - or keep at least one color. It's an easy way to identify bot lines.
08:55 πŸ”— will You could do it as a NOTICE
08:55 πŸ”— Sanqui notices tend to be broken
08:55 πŸ”— will That gives colour as bot
08:55 πŸ”— Sanqui not in hexchat
08:55 πŸ”— Meroje yes notice is better than colours
08:58 πŸ”— PurpleSym Hm, I did not know about NOTICE.
09:01 πŸ”— dan- has joined #archiveteam-bs
09:03 πŸ”— PurpleSym That would be a notice without color.
09:08 πŸ”— dan- has quit IRC (Ping timeout: 260 seconds)
09:15 πŸ”— VADemon has joined #archiveteam-bs
09:24 πŸ”— HCross Anyone else having FOS upload speed issues?
09:26 πŸ”— godane !ao http://imgur.com/a/EYJOW
09:26 πŸ”— godane its in archivebot now
09:29 πŸ”— dan- has joined #archiveteam-bs
09:31 πŸ”— HCross Struggling to get 180kB/s from OVH to FOS atm :/
09:35 πŸ”— schbirid "-purplebot/#archiveteam-bs-" is so long it makes the display in hexchat annoying for me :(
09:37 πŸ”— PurpleSym I doubt we’ll get it right for everyone.
09:44 πŸ”— dxrt looks good to me
10:20 πŸ”— Sanqui yeah, in hexchat it's NG
10:22 πŸ”— dxrt can one of you screenshot?
10:22 πŸ”— dxrt curious, it's just a pretty simple notice
10:28 πŸ”— godane SketchCow: i think this needs to be moved out of netcafe collection : https://archive.org/details/newsmagazineofthescreen1952
10:28 πŸ”— godane i'm just give you note on it
10:30 πŸ”— schbirid https://i.imgur.com/WwSS9ys.png
10:30 πŸ”— schbirid dxrt: ^
10:32 πŸ”— dxrt damn. pretty nice in textual. https://i.imgur.com/hk9OWEW.png
10:43 πŸ”— HCross has quit IRC (Ping timeout: 370 seconds)
10:46 πŸ”— hawc145 has joined #archiveteam-bs
10:48 πŸ”— will textual is so nice http://i.imgur.com/BZWg2gM.png
10:50 πŸ”— schbirid "OS X" heh
10:53 πŸ”— hawc145 is now known as HCross
10:57 πŸ”— schbirid has quit IRC (Quit: Leaving)
11:09 πŸ”— dan- just a note with noticed, some clients like to highlight/ping every notice to a channel as though it's a ping with their nickname in it
11:09 πŸ”— dan- with notices*
11:09 πŸ”— dan- because some clients are very very silly
11:30 πŸ”— schbirid has joined #archiveteam-bs
12:16 πŸ”— HCross Looks like we need a LOT of concurrent on zippcast if its to be done in time
12:40 πŸ”— tfgbd_znc has joined #archiveteam-bs
12:49 πŸ”— godane i'm now uploading MBC Newsdesk for 2002-06-04 to 2002-07-27
12:55 πŸ”— dashcloud HCross: zippcast is a script-only project, or a warrior project?
12:55 πŸ”— Meroje it's the current team's choice on the warriors
12:59 πŸ”— Kazzy HCross: can you see tracker admin page?
13:00 πŸ”— HCross I cant
13:02 πŸ”— schbirid ugh, guys, can someone find me Season 10 of Dallas Cowboys Cheerleaders? asking for a friend. tpb torrents are dead, usenet only has s10e02
13:04 πŸ”— Kazzy ipt also shows up empty, couple htis but no seeders
13:05 πŸ”— HCross Kazzy, I found individual episodes
13:05 πŸ”— HCross on IPT
13:06 πŸ”— Kazzy after the first couple of eps the seeders drop off
13:07 πŸ”— schbirid that site looks pretty scammy tbh
13:08 πŸ”— HCross its one of the biggest private trackers
13:08 πŸ”— schbirid oops :D
13:09 πŸ”— schbirid i am so out of the loop with trackers, got the ones i need for ages and thats it
13:15 πŸ”— schbirid lol, even inside it looks like the early 2000s
14:08 πŸ”— BlueMaxim has quit IRC (Quit: Leaving)
14:26 πŸ”— ranma lol, yeah, they are big from what I hear
14:28 πŸ”— ranma surely they aren't the eye sore tvchaosuk is
14:28 πŸ”— ranma or even bitme
14:35 πŸ”— ranma i'm assuming TheBox (uktv) wasn't backed up?
14:36 πŸ”— ranma that was a pretty big loss
14:58 πŸ”— dashcloud has quit IRC (Read error: Operation timed out)
15:01 πŸ”— dashcloud has joined #archiveteam-bs
15:05 πŸ”— vitzli has quit IRC (Quit: Leaving)
15:14 πŸ”— dashcloud has quit IRC (Read error: Operation timed out)
15:15 πŸ”— dashcloud has joined #archiveteam-bs
16:26 πŸ”— Frogging Is the topic a reference to something?
16:26 πŸ”— Frogging :p
16:43 πŸ”— MrRadar This appears to be the context in which the title was set: http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-02-06,Sat&sel=114#l110
16:44 πŸ”— xmc yep
16:44 πŸ”— xmc that's it
16:44 πŸ”— JesseW has joined #archiveteam-bs
16:49 πŸ”— Frogging hah
17:01 πŸ”— JesseW has quit IRC (Read error: Operation timed out)
18:03 πŸ”— mutoso has joined #archiveteam-bs
18:06 πŸ”— JesseW has joined #archiveteam-bs
18:28 πŸ”— JesseW I would still be interested in participating in a (separated from ArchiveTeam) group that worked on educating both site owners and individual users about backing up their materials. It would certainly be a vast sea of frustration and heartbreak, but, eh, such is life.
19:12 πŸ”— balrog has quit IRC (Read error: Operation timed out)
19:12 πŸ”— Mayonaise has quit IRC (Read error: Operation timed out)
19:12 πŸ”— marvinw has quit IRC (Read error: Operation timed out)
19:12 πŸ”— marvinw has joined #archiveteam-bs
19:12 πŸ”— balrog has joined #archiveteam-bs
19:12 πŸ”— swebb sets mode: +o balrog
19:13 πŸ”— mr-b has quit IRC (Read error: Operation timed out)
19:13 πŸ”— Coderjoe has quit IRC (Read error: Operation timed out)
19:13 πŸ”— phuzion has quit IRC (Read error: Operation timed out)
19:13 πŸ”— beardicus has quit IRC (Read error: Operation timed out)
19:13 πŸ”— Coderjoe has joined #archiveteam-bs
19:13 πŸ”— bwn has quit IRC (Read error: Operation timed out)
19:14 πŸ”— remsen has quit IRC (Read error: Operation timed out)
19:14 πŸ”— RKenshin has joined #archiveteam-bs
19:15 πŸ”— Kenshin has quit IRC (Read error: Operation timed out)
19:15 πŸ”— botpie91 has quit IRC (Read error: Operation timed out)
19:15 πŸ”— RKenshin is now known as Kenshin
19:15 πŸ”— dxrt has quit IRC (Read error: Operation timed out)
19:16 πŸ”— _acridAxd has joined #archiveteam-bs
19:16 πŸ”— acridAxid has quit IRC (Read error: Operation timed out)
19:16 πŸ”— will has quit IRC (Ping timeout: 633 seconds)
19:16 πŸ”— _acridAxd is now known as acridAxid
19:17 πŸ”— mistym- has joined #archiveteam-bs
19:18 πŸ”— mistym has quit IRC (Ping timeout: 633 seconds)
19:18 πŸ”— JesseW has quit IRC (Ping timeout: 370 seconds)
19:18 πŸ”— tfgbd_znc has quit IRC (Read error: Operation timed out)
19:20 πŸ”— mr-b has joined #archiveteam-bs
19:20 πŸ”— botpie91 has joined #archiveteam-bs
19:20 πŸ”— remsen has joined #archiveteam-bs
19:20 πŸ”— dxrt has joined #archiveteam-bs
19:21 πŸ”— Mayonaise has joined #archiveteam-bs
19:22 πŸ”— beardicus has joined #archiveteam-bs
19:22 πŸ”— bwn has joined #archiveteam-bs
19:22 πŸ”— phuzion has joined #archiveteam-bs
19:24 πŸ”— tfgbd_znc has joined #archiveteam-bs
19:24 πŸ”— will has joined #archiveteam-bs
19:27 πŸ”— Mayonaise has quit IRC (Read error: Operation timed out)
19:27 πŸ”— botpie91 has quit IRC (Read error: Operation timed out)
19:28 πŸ”— phuzion has quit IRC (Read error: Operation timed out)
19:28 πŸ”— beardicus has quit IRC (Read error: Operation timed out)
19:28 πŸ”— botpie91 has joined #archiveteam-bs
19:29 πŸ”— phuzion has joined #archiveteam-bs
19:30 πŸ”— Mayonaise has joined #archiveteam-bs
19:30 πŸ”— beardicus has joined #archiveteam-bs
19:34 πŸ”— pluesch has joined #archiveteam-bs
19:36 πŸ”— JesseW has joined #archiveteam-bs
19:43 πŸ”— ErkDog HCross2 HCross you around?
19:56 πŸ”— tomwsmf-a has joined #archiveteam-bs
20:03 πŸ”— schbirid has quit IRC (Quit: Leaving)
20:05 πŸ”— JesseW has quit IRC (Ping timeout: 272 seconds)
20:21 πŸ”— JesseW has joined #archiveteam-bs
20:24 πŸ”— VADemon has quit IRC (Quit: left4dead)
20:27 πŸ”— VADemon has joined #archiveteam-bs
20:39 πŸ”— Aranje has joined #archiveteam-bs
21:06 πŸ”— bwn has quit IRC (Ping timeout: 244 seconds)
21:18 πŸ”— bwn has joined #archiveteam-bs
21:19 πŸ”— ndiddy can someone here do me a favor?
21:20 πŸ”— ndiddy i'd like to find a scan of the september 5, 1983 issue of newsweek
21:35 πŸ”— bwn has quit IRC (Read error: Connection reset by peer)
22:12 πŸ”— bwn has joined #archiveteam-bs
22:26 πŸ”— Guest56 has joined #archiveteam-bs
22:27 πŸ”— Guest56 has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
22:37 πŸ”— ZiNC has joined #archiveteam-bs
22:37 πŸ”— ZiNC Hi.
22:52 πŸ”— Frogging hi
22:53 πŸ”— ZiNC :)
22:53 πŸ”— ZiNC Not sure if the topic is more appropriate there or here.
22:53 πŸ”— Frogging probably here if it's to continue
22:55 πŸ”— ZiNC What's actually the distinction? What sort of stuff happens in #archiveteam?
22:55 πŸ”— MrRadar #archiveteam is a low-volume channel for discussing sites that are actively in danger or are actively being archived
22:55 πŸ”— MrRadar This is for everything else ArchiveTeam related
22:56 πŸ”— ZiNC E.g., "Excite is about to close, must act now!"?
22:56 πŸ”— MrRadar Yes, exactly
22:56 πŸ”— MrRadar Though some discussion ends up happening there every once in a while
22:57 πŸ”— ZiNC Speaking of Excite, it's surprisingly mid-90s yet still alive
22:57 πŸ”— Frogging we generally try and keep #archiveteam low-traffic, and spin off projects into their own channels
22:57 πŸ”— MrRadar Wow, you are not kidding
22:58 πŸ”— ZiNC You can get there an email box without giving a phone number. Not something you find every day. :)
22:58 πŸ”— ZiNC Well, I think you can.
22:59 πŸ”— ZiNC Did AT archive forums where by default it only shows messages from the last N days?
23:00 πŸ”— ZiNC I wonder what's the solution to that. Other than doing stuff manually, or adding logic which is specific per forum software/version.
23:03 πŸ”— JesseW So, about extracting stuff from the Wayback Machine --
23:03 πŸ”— JesseW as MrRadar mentioned, you can search the list of URLs saved via the CDX server.
23:04 πŸ”— ZiNC Thanks. Playing with that now.
23:04 πŸ”— JesseW and you can get the URL response unmodified by appending id_ to the timestamp part
23:04 πŸ”— ZiNC Their FAQ mentioned that searching is still not possible. But there was a mentioned of something years ago, so I figured maybe the FAQ's out of date.
23:05 πŸ”— JesseW e.g. https://web.archive.org/web/20060716155041id_/http://example.com/?
23:06 πŸ”— JesseW So, combining both of those together, you should be able to hack together something more or less like searching.
23:06 πŸ”— JesseW at a minimum, you can download all the responses and search them locally
23:06 πŸ”— ZiNC Is there any etiquette on mass downloading of pages?
23:06 πŸ”— ZiNC at archive.org.
23:07 πŸ”— JesseW the basic etiquette is: "Take it, that's why we exist"
23:08 πŸ”— ZiNC Their basic user-oriented web interface is commonly slow to show archived pages, so I guess bandwidth or resources needed for retrieval aren't abundant.
23:09 πŸ”— JesseW If you want to, you could use a custom User-Agent that lists a contact email address for yourself, and/or send an email to info@archive.org ahead of time mentioning what you're planning to download -- but nothing is required or expected, AFAIK.
23:10 πŸ”— JesseW Yeah, it's not speedy -- so probably putting in as much of a delay as you are comfortable with would probably be kind -- but the point remains that IA is a very firm believer in "access drives preservation" -- so they're glad anytime someone downloads stuff.
23:11 πŸ”— ZiNC BTW, something I else I was reminded of.
23:11 πŸ”— ZiNC Are there non-Usenet NNTP archives somewhere?
23:12 πŸ”— JesseW Not that I know of...
23:13 πŸ”— ZiNC Does this sound something interesting to archive? There may have been a few "local" forums that worked that way.
23:19 πŸ”— JesseW It's certainly worth making copies of.
23:20 πŸ”— JesseW Depending on how visible it was when it was up, and how long ago that was, I might lean towards keeping those copies private for a while -- but better to get copies in any case.
23:24 πŸ”— ZiNC Unless server owners kept the messages, the only way would be to somehow collect whatever partial local copies the people subscribed have.
23:25 πŸ”— ZiNC Going over some old emails I found an Outlook Express DBX for such a newsgroup.
23:25 πŸ”— ZiNC The program I used to extract emails from DBX ignored the contents of a newsgroup DBX. But another utility did extract it.
23:33 πŸ”— JesseW has quit IRC (Ping timeout: 370 seconds)
23:34 πŸ”— ZiNC Any idea if it's possible to use archive.org's CDX to search for URLs that contain a certain text in a random location? Such a parameter doesn't seem to work: filter=original:text
23:34 πŸ”— ZiNC "original" is the name of the original URL field, text is supposedly a regexp.
23:44 πŸ”— bwn has quit IRC (Read error: Operation timed out)
23:46 πŸ”— botpie91 has quit IRC (Read error: Operation timed out)
23:46 πŸ”— beardicus has quit IRC (Read error: Operation timed out)
23:47 πŸ”— ErkDog hey ZiNC do you have any *NIX systems around with spare bandwidth/resources?
23:48 πŸ”— ZiNC Can't say that I do.
23:48 πŸ”— ZiNC No special hardware or connection here...
23:48 πŸ”— tfgbd_znc has quit IRC (Ping timeout: 633 seconds)
23:48 πŸ”— botpie91 has joined #archiveteam-bs
23:49 πŸ”— phuzion has quit IRC (Read error: Connection reset by peer)
23:49 πŸ”— tfgbd_znc has joined #archiveteam-bs
23:49 πŸ”— ErkDog you got enough resources/bandwidth on your windows box to run a small VM?
23:50 πŸ”— phuzion has joined #archiveteam-bs
23:50 πŸ”— beardicus has joined #archiveteam-bs
23:51 πŸ”— ZiNC Just a home connection, and they're rather stingy in upsteam around here. :)
23:51 πŸ”— ZiNC What are you trying to do?
23:51 πŸ”— ZiNC upstream
23:52 πŸ”— bwn has joined #archiveteam-bs

irclogger-viewer