00:36:06kansei quits [Quit: ZNC 1.10.1 - https://znc.in]
00:56:19kansei (kansei) joins
01:25:18DogsRNice joins
02:55:30Exorcism|irc quits [Quit: Ping timeout (120 seconds)]
02:55:45DigitalDragons quits [Quit: Ping timeout (120 seconds)]
02:56:10Exorcism|irc (exorcism) joins
02:58:32DigitalDragons (DigitalDragons) joins
05:26:25tek_dmn quits [Quit: ZNC - https://znc.in]
05:28:12tek_dmn (tek_dmn) joins
05:35:02DogsRNice quits [Read error: Connection reset by peer]
06:32:09IDK quits [Quit: Connection closed for inactivity]
07:17:13sec^nd quits [Ping timeout: 276 seconds]
07:18:23sec^nd (second) joins
07:28:35second (second) joins
07:28:36sec^nd quits [Remote host closed the connection]
07:28:46second is now known as sec^nd
10:57:27vex20k joins
10:59:16vex20k quits [Client Quit]
12:00:00Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat]
12:02:49Bleo182600722719623455222 joins
12:48:10IDK (IDK) joins
13:34:34BlueBlaziken joins
13:35:48w0rm (w0rm) joins
13:42:41<BlueBlaziken>Hello, it seems that across multiple projects (Gooblog and Telegram tried so far), across different internet connections, and even across different usernames, the Warrior fails to archive things? Some projects say that my IP is banned (I'm using residential and mobile data connections for my testing, no VPNs or anything in use, and both have worked just fine for me in the past), while sometimes
13:42:47<BlueBlaziken>there are other errors about failing to connect to rsync servers (connection refused, 111) and other such weirdness. Did I do anything horribly wrong to get IP banned somehow, or are these shared issues happening across AT infrastructure? My Warrior username is AnotherMemberOfTheHivemind if you all need that
13:45:40<w0rm>I think the main issue is: transfer.archivete.am. 120 IN A 127.0.0.1 , and I think the team is aware of it
13:45:57<BlueBlaziken>So it is on their end, you reckon?
13:47:02<BlueBlaziken>I see Telegram tracker slow to a crawl on new jobs assigned, but can't tell if it's just some client side sync weirdness or if jobs genuinely aren't being assigned
13:52:30<cruller>My gooblog-grab container is reporting Failed to resolve 'transfer.archivete.am' ([Errno -3] Temporary failure in name resolution)")), so it should be a server-side issue.
14:10:08<cruller>Ah, that aside, goo is currently blocking access from outside Japan. This is a project-specific issue, so the details will be discussed in #itsgoone.
15:56:39Guest58 quits [Quit: My Mac has gone to sleep. ZZZzzz…]
16:05:29Webuser506533 joins
16:07:50<Webuser506533>The CNAME record for transfer.archivete.am has disappeared from DNS, and the A record is returning 127.0.0.1, causing the archive bot to stop functioning.
16:09:30<Webuser506533>https://dnschecker.org/#CNAME/transfer.archivete.am
16:09:32trc quits [Remote host closed the connection]
17:05:36cyanbox quits [Read error: Connection reset by peer]
17:05:58cyanbox joins
17:10:13cyanbox quits [Read error: Connection reset by peer]
20:13:09yano quits [Quit: WeeChat, https://weechat.org/]
20:15:18yano (yano) joins
21:01:04DogsRNice joins
21:20:02cyanbox joins
22:59:26Meli quits [Killed (NickServ (GHOST command used by Meli-sama))]
23:01:20Shard79 quits [Quit: Im doing something rq. Il brb]
23:01:37Meli (Meli) joins
23:05:29Shard79 (Shard) joins
23:06:26Meli quits [Ping timeout: 256 seconds]