[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] Tumblr dump probably just went public: https://mega.nz/#!V9ZmSCCS!lRgT4irycFEefJvWVm0-xZOuhNRZP7Hg41rJJuydSQY [02:28] Grabbing right now, going to verify and then throw up on IA [02:54] 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] is that the password leak [02:55] if so, why are you being a dick [03:03] 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] (and Troy Hunt already has the data in ihavebeenpwned, so) [03:05] ugh, would have grabbed if less than half a gig [03:11] *** Start has quit IRC (Ping timeout: 260 seconds) [03:13] yipdw: yeah? I don't see it in there https://haveibeenpwned.com/PwnedWebsites [03:13] I see a tumblr breach from 2013 [03:14] that's what I'm asking about [03:14] there was a 2013 data breach that was made public May 30 [03:14] oh I see [03:14] of this year [03:14] ah that was my confusion then. I didn't realize the data breach was that long ago [03:14] I wonder where it sat around for 3 years [03:15] probably with people who knew the value of STFU [03:16] SHA1 [03:16] oh dear [03:16] 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] is it just too big for anybody to attempt to steal and this is the only thing that makes economic sense? [03:17] dunno [03:17] 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] I do but I made it after 2013 [03:18] yipdw: if that were the case it would have been made public 3 years ago. [03:18] maybe [03:18] 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] IA definitely has no reason to be hosting this. [03:19] ^ [03:20] lol fur affinity is considered a "sensitive breach" on HIBP [03:21] makes sense [03:21] The full source code of their site leaked due to ImageTragick and apparently their DB was partly wiped [03:21] idk, it's not technically a dodgy site [03:21] not sure how this is different from any other leaked data? [03:21] especially given that the risk involved in a credential leak very rapidly goes down [03:21] once it starts becoming semi-public [03:21] what's the historical value of it thought joepie91 [03:22] (that is, people have pillaged it for all the interesting stuff already) [03:22] though* [03:22] 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] 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] 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] well, space might be saved 7zipping it [03:23] 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] +have [03:23] yipdw: it isn't anymore, really [03:23] it's been sold for a while now [03:23] the usefulness from a malicious perspective has pretty much disappeared [03:24] i think there's still malicious use available [03:24] 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] ranma: such as? [03:25] one on one targeted abuse [03:25] 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] 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] maybe the owner of that Tumblr is dead [03:25] Especially if it contains links between the user's account and the e-mail it was registered with (does Tumblr require that?) [03:25] because of password reuse [03:26] MrRadar: you log in with your email address [03:26] OK, so they definitely do [03:26] fortunately it doesn't have the yahoo "give us your cellphone" cancer [03:26] (I don't have a Tumblr account, if that wasn't obvious) [03:27] 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] 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] even if you factor out the password-username-linking-problem [03:28] it DOES seem useful for those analysing password use [03:28] white hat/curiosity [03:30] the black/white hat usage of that data seems to be trending towards dark at the moment. [03:30] speaking of illegal-in-some-countries use, i wonder if any FOSS people/groups/communities are collecting bluray encryption keys [03:31] considering AnyDVD HD's successor is requiring rebuying licenses [03:32] oh, has anyone backed up the doom9 messageboard? [03:32] That one's tricky because by default it only shows you the threads active in the last 30 days [03:33] Ah, it has an "archive" link that links them all [03:33] &daysprune=-1 [03:33] nice [03:33] 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] I've seen friendships wrecked over it [03:34] you can argue it wasn't a friendship etc etc but I think that's aside the point [03:34] er, make the breach SENSITIVE [03:34] holy fuck is my keyboard dropping words now or am I just seeing things that I didn't write [03:34] yeah, I think you're right [03:36] 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] the fine line of expectation of privacy/data security [03:37] but also being responsible for putting that information out there [03:38] * yipdw shrugs [03:38] 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] I mean if you want to, fantastic [03:40] http://www.furaffinity.net/tos [03:40] 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] i wonder if they used to imply privacy/discression [03:42] too lazy to research [03:57] it's basically implied. [03:57] *** bwn has quit IRC (Read error: Operation timed out) [03:58] 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] 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] Just ban the bot if that gets too annoying. [08:52] it could have its own channel [08:53] Just a note, the green highlight makes the text impossible to read on a black background [08:53] Well the text is unreadable basically with that bot [08:53] I can remove colors. [08:54] I approve of the bot [08:55] Wrt separate channel: I think Sanqui’s idea was to “connect” wiki and IRC. [08:55] Keep the colors - or keep at least one color. It's an easy way to identify bot lines. [08:55] You could do it as a NOTICE [08:55] notices tend to be broken [08:55] That gives colour as bot [08:55] not in hexchat [08:55] yes notice is better than colours [08:58] Hm, I did not know about NOTICE. [09:01] *** dan- has joined #archiveteam-bs [09:03] 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] Anyone else having FOS upload speed issues? [09:26] !ao http://imgur.com/a/EYJOW [09:26] its in archivebot now [09:29] *** dan- has joined #archiveteam-bs [09:31] Struggling to get 180kB/s from OVH to FOS atm :/ [09:35] "-purplebot/#archiveteam-bs-" is so long it makes the display in hexchat annoying for me :( [09:37] I doubt we’ll get it right for everyone. [09:44] looks good to me [10:20] yeah, in hexchat it's NG [10:22] can one of you screenshot? [10:22] curious, it's just a pretty simple notice [10:28] SketchCow: i think this needs to be moved out of netcafe collection : https://archive.org/details/newsmagazineofthescreen1952 [10:28] i'm just give you note on it [10:30] https://i.imgur.com/WwSS9ys.png [10:30] dxrt: ^ [10:32] 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] textual is so nice http://i.imgur.com/BZWg2gM.png [10:50] "OS X" heh [10:53] *** hawc145 is now known as HCross [10:57] *** schbirid has quit IRC (Quit: Leaving) [11:09] 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] with notices* [11:09] because some clients are very very silly [11:30] *** schbirid has joined #archiveteam-bs [12:16] 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] i'm now uploading MBC Newsdesk for 2002-06-04 to 2002-07-27 [12:55] HCross: zippcast is a script-only project, or a warrior project? [12:55] it's the current team's choice on the warriors [12:59] HCross: can you see tracker admin page? [13:00] I cant [13:02] 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] ipt also shows up empty, couple htis but no seeders [13:05] Kazzy, I found individual episodes [13:05] on IPT [13:06] after the first couple of eps the seeders drop off [13:07] that site looks pretty scammy tbh [13:08] its one of the biggest private trackers [13:08] oops :D [13:09] i am so out of the loop with trackers, got the ones i need for ages and thats it [13:15] lol, even inside it looks like the early 2000s [14:08] *** BlueMaxim has quit IRC (Quit: Leaving) [14:26] lol, yeah, they are big from what I hear [14:28] surely they aren't the eye sore tvchaosuk is [14:28] or even bitme [14:35] i'm assuming TheBox (uktv) wasn't backed up? [14:36] 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] Is the topic a reference to something? [16:26] :p [16:43] 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] yep [16:44] that's it [16:44] *** JesseW has joined #archiveteam-bs [16:49] 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] 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] 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] can someone here do me a favor? [21:20] 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] Hi. [22:52] hi [22:53] :) [22:53] Not sure if the topic is more appropriate there or here. [22:53] probably here if it's to continue [22:55] What's actually the distinction? What sort of stuff happens in #archiveteam? [22:55] #archiveteam is a low-volume channel for discussing sites that are actively in danger or are actively being archived [22:55] This is for everything else ArchiveTeam related [22:56] E.g., "Excite is about to close, must act now!"? [22:56] Yes, exactly [22:56] Though some discussion ends up happening there every once in a while [22:57] Speaking of Excite, it's surprisingly mid-90s yet still alive [22:57] we generally try and keep #archiveteam low-traffic, and spin off projects into their own channels [22:57] Wow, you are not kidding [22:58] You can get there an email box without giving a phone number. Not something you find every day. :) [22:58] Well, I think you can. [22:59] Did AT archive forums where by default it only shows messages from the last N days? [23:00] 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] So, about extracting stuff from the Wayback Machine -- [23:03] as MrRadar mentioned, you can search the list of URLs saved via the CDX server. [23:04] Thanks. Playing with that now. [23:04] and you can get the URL response unmodified by appending id_ to the timestamp part [23:04] 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] e.g. https://web.archive.org/web/20060716155041id_/http://example.com/? [23:06] So, combining both of those together, you should be able to hack together something more or less like searching. [23:06] at a minimum, you can download all the responses and search them locally [23:06] Is there any etiquette on mass downloading of pages? [23:06] at archive.org. [23:07] the basic etiquette is: "Take it, that's why we exist" [23:08] 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] 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] 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] BTW, something I else I was reminded of. [23:11] Are there non-Usenet NNTP archives somewhere? [23:12] Not that I know of... [23:13] Does this sound something interesting to archive? There may have been a few "local" forums that worked that way. [23:19] It's certainly worth making copies of. [23:20] 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] Unless server owners kept the messages, the only way would be to somehow collect whatever partial local copies the people subscribed have. [23:25] Going over some old emails I found an Outlook Express DBX for such a newsgroup. [23:25] 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] 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] "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] hey ZiNC do you have any *NIX systems around with spare bandwidth/resources? [23:48] Can't say that I do. [23:48] 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] 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] Just a home connection, and they're rather stingy in upsteam around here. :) [23:51] What are you trying to do? [23:51] upstream [23:52] *** bwn has joined #archiveteam-bs