HomeSearchPrevious dayNext day

00:16:43m0nika quits [Quit: Zzz]
00:18:03m0nika (m0nika) joins
00:27:46Arcorann (Arcorann) joins
00:28:21godane joins
00:29:18godane1 quits [Ping timeout: 250 seconds]
00:31:44nostalgebraist quits [Client Quit]
00:37:50BlueMaxima joins
01:02:44dm4v_ joins
01:04:05dm4v quits [Ping timeout: 258 seconds]
01:04:05dm4v_ is now known as dm4v
01:04:05dm4v quits [Changing host]
01:04:05dm4v (dm4v) joins
01:26:45AlsoHP_Archivist joins
02:02:16driib8 (driib) joins
02:04:16driib quits [Ping timeout: 258 seconds]
02:04:16driib8 is now known as driib
02:38:52ThreeHM quits [Ping timeout: 250 seconds]
02:40:39ThreeHM (ThreeHeadedMonkey) joins
02:58:39DogsRNice quits [Read error: Connection reset by peer]
02:58:42Viniter quits [Ping timeout: 258 seconds]
03:11:46qw3rty__ joins
03:12:05HackMii quits [Remote host closed the connection]
03:12:37HackMii (hacktheplanet) joins
03:14:51HackMii quits [Remote host closed the connection]
03:15:16qw3rty_ quits [Ping timeout: 250 seconds]
03:15:17HackMii (hacktheplanet) joins
03:22:15HackMii quits [Remote host closed the connection]
03:25:03HackMii (hacktheplanet) joins
04:04:08DopefishJustin quits [Remote host closed the connection]
04:08:34DopefishJustin joins
04:11:49<@OrIdow6>So thinking about all the close calls and close misses, I wonder if it's possible to have something that scans sites and looks for shutdown notice
04:12:20<@OrIdow6>Have some big regex to look for notices, and scan each page in a list once a day, or something like that
04:12:28Viniter (Viniter) joins
04:17:43<@JAA>That probably wouldn't work very well, but something I've had in my head for a long time is a system that scrapes search engines, social media, etc. for relevant terms. I did that manually every couple weeks for a while some years back, but it becomes exhausting very, very quickly. A more sensible approach would probably be to feed into an issue tracker for result management with some basic dedupe.
04:18:20<@JAA>Search examples: 'website closing', 'website "shutting down"', etc.
04:24:37<@OrIdow6>Yes, search engines and social media would help a lot as well; why don't you think a direct check wouldn't work well? Just a low success rate
04:24:55<@OrIdow6>Issue tracker might be useful even without automation
04:25:18<@OrIdow6>Though the wiki does well enough for that, I suppose
04:25:34<@OrIdow6>*rate?
04:26:43<@JAA>Well, for a start, we'd need a big list of websites to check. And that list would have to be kept up-to-date. It's hard (or rather, expensive) enough to get lists of domains, but sometimes a domain hosts multiple websites etc.
04:27:22<@JAA>And the regex would probably be horrible. lol
04:28:06<@JAA>Yeah, I've been thinking recently that an issue tracker might help replace Deathwatch somewhat. Due date, assign to someone, brief status updates without creating a full wiki page, etc. Not sure though.
04:42:54<@JAA>But on the other hand, duplicating information isn't useful nor is splitting it up. So probably not that great an idea.
04:45:28<@OrIdow6>Yes, the regex was a bad idea
04:46:30<@OrIdow6>I can see an issue tracker as being useful for small-to-medium sites
04:47:18<tech234a>On a related note it might make sense to make a change notifier for the Google Support website... it might pick up some shutdown notices for Google products
04:47:21<@OrIdow6>Or perhaps just medium - too small to go on Deathwatch, too big to get done in 5 minutes
04:47:50<@JAA>I'd more see it as useful for keeping track at a glance of what needs to be worked on at what priority and who's leading each effort.
04:48:24<@JAA>But it has the potential of leading to wiki neglect and partially moving discussion away from IRC.
04:48:32<@OrIdow6>tech234a: IIRC someone pointed out that Yahoo Answers disappeared from their product page before the shutdown announcement, so something like that could work
04:48:36<@OrIdow6>More generally
04:49:17<thuban>find some way to make deathwatch transclude information from an issue tracker like ted nelson intended
04:49:39<@JAA>Well, Semantic MediaWiki is a thing.
04:49:51<@OrIdow6>Best solution if you had an issue tracker could just be to chastise people for talking too much about non-issue-tracking related stuff on it, as people are shooed out of #archiveteam
04:50:40<@JAA>(And other similar things as well, since SMW might be ridiculously overpowered for this.)
04:51:46<thuban>color me intrigued
04:53:41<tech234a>Yeah I was the one who noticed that Yahoo Answers was removed from the product list before the shutdown :)
04:54:11<tech234a>But yeah some kind of changelogger for various sites would be nice
04:55:21<@JAA>Good luck with that.
04:56:29<tech234a>Yeah HTML can be messy
04:56:37<tech234a>And vary on page load
04:58:07<@JAA>Basically, we'd want to slightly expand the infobox project with a deadline date and priority and then have a sortable and filterable index over the fields there, I think? Plus we'd need some way to collect smaller things that don't need a full wiki page.
04:59:39<@OrIdow6>Small enough a task that it could be doable with a bot
05:00:21<@JAA>I suppose the smaller ones could simply go on one page (like Deathwatch now) with a bunch of infoboxes or a more minimal version of it.
05:00:22<@OrIdow6>That's also more flexible if you want to be able to create entires on either end
05:00:45<@OrIdow6>That owuld work
05:00:50<@JAA>This actually sounds like a fun little project.
05:01:12<@JAA>Then just keep the index updated with Special:RecentChanges and all is well.
05:02:14<@JAA>I've been meaning to overhaul the infobox for a long time anyway.
05:03:43<@JAA>The wiki would remain the single source of truth and go-to place for information about upcoming shutdowns. The index would just make browsing and keeping an overview a bit simpler (and could live on the wiki or externally).
05:04:29<@JAA>Well, I'm off to bed now, but I'll think about this some more tomorrow. :-)
05:06:48<Ryz>It makes me wonder what's the most urgent thing that when addressed, would improve ArchiveTeam~ ><;
05:07:16<Ryz>It can be a bit hard to tell with so much activity spread out~
05:13:34HackMii quits [Remote host closed the connection]
05:13:54HackMii (hacktheplanet) joins
05:45:04AlsoHP_Archivist quits [Ping timeout: 258 seconds]
06:43:56beej (beej) joins
07:03:13AlsoHP_Archivist joins
07:40:27lennier1 quits [Ping timeout: 258 seconds]
07:40:49lennier1 (lennier1) joins
08:04:56spirit joins
08:21:51AlsoHP_Archivist quits [Ping timeout: 258 seconds]
08:53:13Viniter1 (Viniter) joins
08:53:16Viniter quits [Ping timeout: 250 seconds]
08:53:16Viniter1 is now known as Viniter
08:58:34spirit quits [Client Quit]
09:17:29BlueMaxima quits [Read error: Connection reset by peer]
10:58:41beej quits [Client Quit]
11:30:50user777 quits [Ping timeout: 258 seconds]
12:12:36godane quits [Ping timeout: 250 seconds]
13:54:27Deewiant (Deewiant) joins
15:28:31themadpro (themadpro) joins
16:12:58Arcorann quits [Ping timeout: 258 seconds]
16:27:15sverre26 quits [Remote host closed the connection]
16:45:10luckcolors quits [Ping timeout: 258 seconds]
18:07:51themadpro quits [Client Quit]
18:10:30beej joins
18:45:38lukash7 quits [Ping timeout: 250 seconds]
18:49:59AlsoHP_Archivist joins
18:51:18lukash7 joins
18:59:30Wayward quits [Ping timeout: 250 seconds]
19:02:21AlsoHP_Archivist quits [Read error: Connection reset by peer]
19:02:47AlsoHP_Archivist joins
19:10:20rewby quits [Ping timeout: 250 seconds]
19:12:04DogsRNice (Webuser299) joins
20:20:12beej quits [Client Quit]
21:22:09Sylirana quits [Ping timeout: 244 seconds]
21:22:59Sylirana (Sylirana) joins
21:33:24BlueMaxima joins
21:53:43britm0b joins
21:53:45britmob quits [Ping timeout: 258 seconds]
21:58:32rewby (rewby) joins
22:08:50rewby quits [Client Quit]
22:09:24rewby (rewby) joins
22:39:12Matthww quits [Ping timeout: 250 seconds]
22:45:04Matthww joins
22:49:50Matthww quits [Client Quit]
22:50:10Matthww joins
23:04:24britmob joins
23:06:58britm0b quits [Ping timeout: 258 seconds]
23:17:54AlsoHP_Archivist quits [Client Quit]
23:23:24superkuh quits [Ping timeout: 250 seconds]

HomeSearchPrevious dayNext day