00:18:57Stilett0 quits [Remote host closed the connection]
00:53:59qw3rty__ quits [Read error: Connection reset by peer]
00:54:32qw3rty__ joins
00:55:26xit quits [Quit: Ping timeout (120 seconds)]
00:55:49xit joins
00:59:23HP_Archivist quits [Read error: Connection reset by peer]
01:18:27DopefishJustin joins
01:21:33Stiletto joins
01:26:03Ryz quits [Remote host closed the connection]
01:27:56Ryz (Ryz) joins
02:10:10HP_Archivist (HP_Archivist) joins
02:34:59Doran is now known as Doranwen
03:33:22qw3rty_ joins
03:37:08qw3rty__ quits [Ping timeout: 250 seconds]
04:11:16DogsRNice_ quits [Read error: Connection reset by peer]
05:15:26G4te_Keep3r quits [Client Quit]
05:20:19G4te_Keep3r joins
05:50:08Iki1 quits [Read error: Connection reset by peer]
06:43:28HP_Archivist quits [Ping timeout: 250 seconds]
12:23:45Iki joins
15:50:14spirit joins
16:26:41OrIdow6 quits [Ping timeout: 258 seconds]
16:29:09OrIdow6 (OrIdow6) joins
17:23:58spirit quits [Client Quit]
17:38:22DogsRNice (Webuser299) joins
17:49:57HP_Archivist (HP_Archivist) joins
18:42:54<@JAA>Dammit IA... /metadata/item returns an HTTP 200 if the item doesn't exist.
19:19:31<HCross>I presume arkiver will arrange for the relevant person to be arrested for that
19:38:44<@JAA>:-)
21:01:28xit quits [Ping timeout: 250 seconds]
21:15:37<HP_Archivist>Was thinking about the long-term integrity of the knowledge / information / files / websites saved over time into the WBM/Archive.org and a thought occurred the other day
21:15:55<HP_Archivist>Does the Internet Archive have safeguards in place to protected against ransomware attacks?
21:16:06Iki quits [Ping timeout: 258 seconds]
21:16:07<HP_Archivist>protect*
21:17:47<HP_Archivist>I'm assuming if they did they wouldn't publicly disclose / talk about it much. And also that any backups they would have would server as a solution to a ransomware attack
21:17:54<HP_Archivist>serve*
21:29:31HP_Archivist quits [Ping timeout: 258 seconds]
21:55:23HP_Archivist (HP_Archivist) joins
22:58:40<@arkiver>JAA: HCross: thanks, reported
23:48:39<@arkiver>it's been like this for a long time apparently, not unexpected from the IA side
23:58:36<@JAA>Yeah, it's the first time I'm working with this endpoint.