05:04:44fuzzy80211 (fuzzy80211) joins
05:05:12fuzzy8021 quits [Read error: Connection reset by peer]
05:24:25DogsRNice quits [Read error: Connection reset by peer]
08:17:27nicolas17 quits [Ping timeout: 256 seconds]
09:15:11nulldata quits [Quit: So long and thanks for all the fish!]
09:16:29nulldata (nulldata) joins
09:22:57nicolas17 joins
09:38:07driib quits [Quit: The Lounge - https://thelounge.chat]
09:38:31driib (driib) joins
10:41:47pabs quits [Killed (nuke.hackint.org (Nickname regained by services))]
10:41:54pabs (pabs) joins
13:02:29nicolas17 quits [Ping timeout: 256 seconds]
14:36:12nicolas17 joins
16:34:59Lord_Nightmare quits [Ping timeout: 256 seconds]
16:35:46Lord_Nightmare (Lord_Nightmare) joins
16:44:48<@arkiver>yes i believe what datechnoman says
16:45:43<@arkiver>OrIdow6: i don't follow this: "not moving-around" -> "it'd have to be deduplication"
16:49:03<@arkiver>steering: PBs in, PBs out, right :P
17:09:54KoalaBear84 joins
17:13:31KoalaBear quits [Ping timeout: 256 seconds]
17:23:35DogsRNice joins
17:25:12DogsRNice quits [Client Quit]
18:20:00<nicolas17>getting 1.5MiB/s uploads, luxury
19:00:44<OrIdow6>arkiver: (obviously this is not airtight) 4 possibilities for data reduction - move-around, delete, compress, dedup; delete eliminated a priori, and I speculate that e.g. recompressing with zstd might not do much (though again I don't actually know that); so moving-around and dedup are the only ones left
22:54:16<@JAA>> sent 4,112 bytes received 92,819,690,399 bytes 1,168,726.75 bytes/sec
22:54:32<nicolas17>floppy disk per second
22:54:46<@JAA>Yeah lol
22:55:10<@JAA>Some are also running somewhat fast, but yeah, this keeps happening across items.