00:05:06 From a quick look, I see 5 40-ish GB WARCs uploaded. It doesn't _seem_ like we ran a full project, but it should all be in the Wayback Machine. Are you looking for something specific? 01:33:57 I am looking for these 3 links: http://rapidshare.com/files/403120049/BOEth_arghprkl.part1.rar.html http://rapidshare.com/files/403138595/BOEth_arghprkl.part2.rar.html http://rapidshare.com/files/403155124/BOEth_arghprkl.part3.rar.html 02:47:37 No captures for any of those within the date range of the project 03:47:54 what does that mean? 03:48:30 It doesn't appear that our projects captured those. I have one more thing to check here. 03:54:02 Checking the CDX of the files from the project, I don't see that ID appear or the file name anywhere. It's unlikely that we captured it. Sorry. :( 05:37:50 arghprkl, must be finnish 05:46:18 Edmodo is shutting down September 22 https://support.edmodo.com/hc/en-us/articles/8135620675223 05:46:38 Don't think that UGC is publicly accessible though 05:48:55 Ok content under /pages/ and /district/ is accessible 05:50:06 oops, I can't serve my murobbs post finder html+js off archive.org due to CORS 05:50:25 uh, the mime type I mean. the html opens as text :) 05:51:16 and github pages with sqlite in archive.org probably doesn't cut it due to CORS. but I could host the sqlite in github too 05:52:36 https://github.com/maakuth/muropostfinder anyway, here's what i've been cooking. apologies for the real frontend developers who might be around :D 06:16:15 hmm, CORS shouldn't be an issue, html wise... I think that can be resolved on archive.org... 06:20:52 that would be nice. it could be great for this sort of data lookup things if they could be hosted 'backendless' in archive.org 06:27:21 Yes, there's quite a few for other ArchiveTeam projects. 09:17:22 Jake: could you look into it or should I approach archive.org with a request? 15:25:19 arkiver: ^? 16:46:38 i wish wikipedia would articulate a coherent policy for stuff like news articles changing urls 16:49:23 this is the third or fourth time i've tried to chase up a citation, found that the publication reorganized its website and the link 404ed but the article was still up, and had to choose between updating the citation to use the new link and putting in the archived original url 16:55:58 citing only the new url makes it impossible for the reader to verify contents at date of publication, citing only the archived url makes the current page undiscoverable and puts unnecessary load on ia, and citing the new url as "url" and the archived url as "archive-url" is just plain misleading, because there are five different options for "url-status" but none of them 16:56:00 indicate 'the page has moved' 16:57:27 i've waded into wikimedia channels multiple times and never been able to get a clear answer about this, & i am mad 18:48:32 Jake, Maakuth|m: I have had CORS issues before, but that was when accessing the WBM for my Picosong tool. The workaround was to get the thing into the WBM so it's served from the same domain and CORS becomes irrelevant. SPN doesn't support archive.org URLs though (for good reason), so that's actually tricky to do, too. 18:49:42 Actually yeah, archive.org sends the CORS header, but the individual storage servers do not, and those are the ones you need to access. So same issue there. 18:50:10 But if you put everything into the same item and use relative URLs for the requests, that should be fine since CORS wouldn't apply. 18:51:16 (Relative URLs aren't strictly necessary, obviously, but items get moved between servers and are served from two different servers, so you really should.)