#Sciop hit a Petabyte (actually a Pebibyte but nobody knows that word) of total proven capacity a week or two ago. That's all the seeders * the size of the things they are seeding. All volunteers, zero dollars in funding, piggybacking off existing resources wherever we can, run on a donated VPS. This is before we even get into federating archives and are still nailing down the basics of the site.
Peer to peer archives are real and they work, period. 216TiB of threatened cultural, climate, queer, and historical information held in common. That's a people powered archive, and you're welcome in it - to take from, to add to, and help sustain if you can.
Edit: if this is the first you're hearing of sciop, it's at https://sciop.net
@jonny proud to be 100TB of that, and I have some more drives sitting in a box that I need to install
@ricci
Hell yeah baby. We need to get public chat happening to bring the seeders in convo with each other, because there have been some issues with disappearing torrents in qbt clients (distressing, like any v2 torrent larger than a few hundred GB will just poof with default settings) and lots of guide work to do helping ppl set up seedboxes. We're going to write a client bc it turns out the state of libtorrent and clients is basically stasis, and we want to make something that's still living and experimenting - actually implement mutable torrents, use new holepunching methods, and so on.
@jonny Yeah would be very interested in participating; I had to abandon qbit because it seems to have serious problems on FreeBSD, it was chewing through the full 128 GB of RAM I have in that machine and sending the entire machine into swapping hell. But transmission has not been exactly stable with almost 1k torrents....
@ricci
It turns out that qbt/libtorrent just store the entire humongous merkle tree down to the 16KiB block hash for every v2 torrent in memory: https://github.com/arvidn/libtorrent/issues/8012
which is atrocious and unnecessary since the entire point of piece sizes and merkle trees in general is that you do not need to do that. That issue going unresponded to was the thing that tipped me over the edge into "we need to write our own client ASAP" because it turns out we are very far past the limits of what clients are used for most commonly, torrenting ~10GB movies with v1 only.
Bigger downloads, bigger pipes, bigger files = massive burn to planet... 
? 🌳 / :earth ?
@jonny @ricci "~10GB movies with v1 only."
Just torrenting anything 10gb+ seems crazy in itself / little bit sick.
Can imagine some emergency things or exceptions but seems just getting out of hand with all this #tech and everyone stepping up more and more storage (based on #US space btw - / #Amazon #S3 etc)
You wouldn't notice the #environmental #damage of speed (apart from initial digging of roads, upgrades etc) even if the speeds make it seem less damage it's still firing more bits, up and down stream - megs and Gb's now, often streaming repeatedly and for near nothing and over-quality. Temporary.
Bigger downloads, bigger pipes, bigger files = massive burn to planet... ? 🌳 / :earth ?
What do you think of that? ⬆️
