So much #debian to seed :D

I have been planning this since last fall, but the coming #YouTube lockdown has finally gotten me to request an account on a #PeerTube instance! To start I will reupload content from my old channels, but I hope to eventually return to livestreaming (also on PeerTube and/or with #Owncast, since I won't be using #Twitch any more either). I am also thinking about getting a #seedbox and having magnet links to torrents of all my stuff, but since I know that PeerTube uses #webtorrent, I'm wondering if I can just get a magnet link for my video from my PeerTube instance and pass it to the seedbox.

Of all the #torrent #BitTorrent traffic I seed, by far the heaviest is a single 300 GiB portion of Anna's Archive. I suspect that various AI companies are constantly downloading the archive. Example here is a peer that, supposedly, is using a dev build of #anacrolix. #AnnasArchive.

#Meta (#Facebook) accusé d'avoir piraté des films #porno... pour entrainer son #IA

Meta a littéralement été prise la main dans le sac. Deux producteurs de contenus pour adultes l'accusent de piratage massif : elle aurait téléchargé des milliers de leurs vidéos via #BitTorrent pour entraîner ses modèles d’intelligence artificielle (IA).

https://www.clubic.com/actualite-574455-meta-facebook-accuse-d-avoir-pirate-des-films-porno-pour-entrainer-son-ia.html

Por favor: sembrad esta maravilla clásica. Gran musical de comedia ¡y terror! #BitTorrent #LaTiendaDeLosHorrores 1986 de Frank Oz.

if anyone is bored or wants to contribute to gray archive tech, i've done all the hard parts around this, but here is a set of things you could do to make "practical repack mutability for torrents" happen: https://codeberg.org/Safeguarding/-/projects/19508

so we have an indexer and a cli tool that can interact with clients. if we added one link table that allowed people to declare relationships between torrents - like e.g. if one replaces another, or is an updated version of, successor to, and so on, then one could plug in the pieces so the cli periodically checks for updated versions of torrents and swaps them out in the local client.

this could be your name in the credits: "what if bittorrent trackers weren't just static repositories of torrent files and generic peer connection machines but could facilitate socio-technological resolutions to basic problems in the protocol."

I just closed da loop on the first example of the distributed, bittorrent backed, "archiveteam-warrior except anyone can do it and not necessarily have uploading to archive org being the only means of sharing". .. thing. And it's pretty good. In a couple months we've slowly spread our octopus tentacles over the whole bittorrent/scraping stack and it's cool to start seeing the pieces connect.

We have a basic problem: someone recognizes a dataset will disappear, then we would have to have a whole convoluted forum process where we post what we're taking, blah blah heroism, volunteerism, solving hard problems on the fly, love this group. Except that sometimes only half the data would show up, or it would end up with one person needing to seed 20TB from their home connection. So uneven labor distribution

Anyway once we get the frontend and docs writ we'll have a sketch of an idea: what if not just distributing the data, we also distributed the scraping. making it possible for deduplicated, distributed crawl tasks that feed automatically back into feeds of torrents. Once we convince arvindn to make webtorrent enabled by default, we've got some cool news with the replayweb.page folks to share. Along with being able to share the work and mutually validating snapshots of the web, that's your distributed wayback machine.

Then it's time to start the federation part where it gets really interesting - making AP groups that can mutually coordinate archival work and publish it in private, overlapping torrent bubbles

Edit: here is the thing in code form, docs are the cherry on top: https://codeberg.org/Safeguarding/-/projects/18027

#qBittorrent 5.1.1 Open-Source #BitTorrent Client Improves #Wayland Support on #Linux https://9to5linux.com/qbittorrent-5-1-1-open-source-bittorrent-client-improves-wayland-support

posted in the "why is webtorrent not implemented in libtorrent" issue and have incited generational warfare among the pirates
https://github.com/arvidn/libtorrent/issues/7283#issuecomment-2911287354

here is a sneak preview of a very simple python package for creating and handling .torrent files.

https://torrent-models.readthedocs.io/en/latest/

https://github.com/p2p-ld/torrent-models

• Full v2 and hybrid torrent support.
• model-based validation, editing, and parsing with modern python type annotations and metadata.
• Reasonable to use object when loaded with kind serdes handling (not just a wrapper around a bytestring dict)
• Fast enough to use with a tracker/web service (a surprising amount of the existing packages have O(n2) spots for no reason, this is ~dozens-thousands of times faster than torf).
• TODO: implement the rest of the BEPs, add methods for partial rehashing, more testing.

I was surprised this needed to be written since torrents are a relatively simple file format, but it did - none of the existing packages are suited for use as a library e.g. for tracker/client software and most can only do v1. I wrote this for sciop, where we want to be experimenting on the format, but also do stuff like dynamically modifying torrents to add trackers, webseeds, and other metadata. I'll do a full announcement after implementing the rest of the BEPs.

Say what you will, but we need more #bittorrent used. Especially version 2 of protocol. Immensely powerful for distributed file sharing with updates!

But we also need good trackers. And of course #elixirlang has an implementation of one now.

https://github.com/Dahrkael/ExTracker