HomeSearchPrevious dayNext day

00:00:14<thuban>Wayward: you're late https://ircv3.net/
00:00:36<Wayward>that's just irc 1.0.3
00:00:57<@JAA>https://xkcd.com/927/
00:01:32<Wayward>:)
00:02:01<@JAA>IRCv3 fixes many of the issues with IRC, and there are drafts for additional parts that will fix more, including session resumption. I don't think it'll move to UDP anytime soon if ever. Not very sensible really.
00:02:11<Wayward>what we need is IMAP for IRC (en capslock)
00:02:43<@JAA>All kinds of core stuff would have to be completely rewritten. And at that point, you might as well just write a new chat protocol, aka xkcd 927.
00:03:22Barto (Barto) joins
00:03:46<Wayward>the main issue is nobody wants to write a server that hosts user session data without becoming its own product (ie, irccloud)
00:03:57<Wayward>(basically, imap for irc)
00:24:17Barto quits [Ping timeout: 244 seconds]
00:29:56Barto (Barto) joins
00:36:55tzt quits [Ping timeout: 252 seconds]
01:05:37Church quits [Ping timeout: 265 seconds]
01:05:45<@hook54321>I kinda wanna try Quassel, but the desktop app doesn't look goood.
01:12:19hooway quits [Client Quit]
01:19:12tzt joins
01:30:34benjinsmith is now known as benjins
01:35:08BlueMaxima quits [Client Quit]
01:44:41Jens quits [Quit: Jens]
01:45:05Jens (JensRex) joins
02:24:24<systwi_>Does archivebot support ftp links?
02:24:34<systwi_>Sorry for the dumb question.
02:24:38systwi_ is now known as wsystwi
02:24:49wsystwi is now known as wystwi
02:25:05wystwi is now known as systwi
02:27:08<@JAA>systwi: Depends on what you mean by 'support'. It can download over FTP, and those jobs will nearly always crash due to bugs.
02:29:02BlueMaxima joins
02:32:28<systwi>So currently throwing in an ftp URL is pretty much a no-go.
02:32:59<@JAA>Yeah, unless it's really small.
02:34:20<systwi>I was asking because I found an FTP server from Compaq/HP (I believe) that has terabytes of drivers/manuals/etc.
02:34:21<@JAA>https://github.com/ArchiveTeam/wpull/issues?q=is%3Aissue+project%3AArchiveTeam%2Fwpull%2F3
02:34:38<@JAA>#effteepee
02:36:24<systwi>Ahh, I see this has been ongoing.
02:37:10<systwi>ftp://15.73.48.59/pub/ in case you're interested. I found it on /r/opendirectories a few months back; forgot the tab was still open
03:12:17aleph joins
03:22:20<Craigle>Would that be the kind of thing we could DPoS? Or not really?
03:28:05nepeat_ joins
03:28:05nepeat quits [Read error: Connection reset by peer]
03:34:48TheLovinator quits [Quit: Ping timeout (120 seconds)]
04:03:31qw3rty__ joins
04:07:21qw3rty_ quits [Ping timeout: 265 seconds]
04:25:10OrIdow6 quits [Ping timeout: 252 seconds]
04:34:41OrIdow6 (OrIdow6) joins
04:48:29DogsRNice quits [Read error: Connection reset by peer]
04:51:01OrIdow6 quits [Ping timeout: 252 seconds]
04:56:21aarchi (aarchi) joins
05:08:17etnguyen03 quits [Client Quit]
05:35:32OrIdow6 (OrIdow6) joins
05:41:44astrid (astrid) joins
05:58:12daalekz (daalekz) joins
06:47:54daalekz quits [Client Quit]
07:19:19Mateon2 joins
07:21:14Mateon1 quits [Ping timeout: 244 seconds]
07:21:15Mateon2 is now known as Mateon1
07:49:16BlueMaxima quits [Client Quit]
07:54:10OrIdow6 quits [Ping timeout: 252 seconds]
07:57:10sec^nd quits [Remote host closed the connection]
07:57:34sec^nd (second) joins
08:01:43mutantmonkey quits [Remote host closed the connection]
08:02:00mutantmonkey (mutantmonkey) joins
08:09:11atphoenix quits [Quit: Leaving]
08:09:49atphoenix (atphoenix) joins
09:02:17OrIdow6 (OrIdow6) joins
09:25:31spirit quits [Client Quit]
10:00:35hooway joins
10:20:00britm0b quits [Ping timeout: 265 seconds]
10:30:59godane joins
10:32:01Barto quits [Ping timeout: 252 seconds]
10:32:45Barto (Barto) joins
10:33:32godane1 quits [Ping timeout: 265 seconds]
10:41:42Barto quits [Ping timeout: 244 seconds]
10:42:13Barto (Barto) joins
11:32:51no112 quits [Ping timeout: 244 seconds]
11:45:04Barto quits [Ping timeout: 265 seconds]
11:47:11Barto (Barto) joins
11:55:03no112 joins
12:01:47OrIdow6 quits [Ping timeout: 244 seconds]
12:25:22OrIdow6 (OrIdow6) joins
14:25:55etnguyen03 (etnguyen03) joins
14:26:30Arcorann quits [Ping timeout: 265 seconds]
15:15:19OrIdow6 quits [Ping timeout: 265 seconds]
15:18:02OrIdow6 (OrIdow6) joins
16:10:34britmob joins
16:11:55aleph quits [Ping timeout: 252 seconds]
16:29:35britmob2 joins
17:12:46nertzy quits [Ping timeout: 265 seconds]
17:13:19onetruth joins
17:14:47godane1 joins
17:15:19<@kiska>> M185 mouse for when my G703 needs charging... https://server8.kiska.pw/uploads/8c1b50a7a075a9d1/image.png
17:15:28<@kiska>> G703 settings https://server8.kiska.pw/uploads/d84fae2ef9e4900e/image.png
17:15:54onetruth quits [Read error: Connection reset by peer]
17:17:06<@kiska>So much better https://server8.kiska.pw/uploads/8c46b164d5f7a20a/image.png
17:17:22godane quits [Ping timeout: 252 seconds]
17:22:42onetruth joins
17:36:37godane1 quits [Ping timeout: 252 seconds]
17:40:26nertzy (nertzy) joins
18:08:10aleph joins
18:49:13OrIdow6 quits [Ping timeout: 252 seconds]
18:51:09OrIdow6 (OrIdow6) joins
18:51:12OrIdow6 quits [Remote host closed the connection]
18:51:41OrIdow6 (OrIdow6) joins
19:43:53hooway quits [Client Quit]
19:45:19hooway joins
20:18:49ThreeHeadedMonkey quits [Ping timeout: 244 seconds]
20:21:01ThreeHeadedMonkey (ThreeHeadedMonkey) joins
20:48:03DogsRNice (Webuser299) joins
21:16:04betamax quits [Ping timeout: 252 seconds]
21:53:36BlueMaxima joins
22:06:39<Wayward>Is there any such thing as generating a parity backup drive, similar to a RAID setup, but taking 3 or 4 or 5 independent stand-alone drives that are set to READONLY and generating a parity disk from them to use for recovery if any of them should fail?
22:15:33dbgft joins
22:35:02daalekz (daalekz) joins
23:32:41hooway quits [Client Quit]
23:46:47Arcorann (Arcorann) joins

HomeSearchPrevious dayNext day