torrents.csv is from a GitLab repository of @Dessalines ?
You could call it decentralized in the sense that the data is hosted in git and anyone can do pull requests to add torrents. But “federated” data storage is tricky because you need some approval / trust method of adding data, otherwise anyone could add a lot of crap / noise to it. This is why most modern torrent trackers / sites have difficult signups.
BTW heres the repo: https://codeberg.org/heretic/torrents-csv-data/
Sorry, I got the link shared by @miguel@lemmy.ml: https://github.com/awesome-selfhosted/awesome-selfhosted#peer-to-peer-filesharing
I thought that was on root though
Awesome Selfhosted: peer-to-peer filesharing list https://github.com/awesome-selfhosted/awesome-selfhosted#peer-to-peer-filesharing
many of those are very interesting.
but I fail to see which of those are “federated”
Hmm, I don’t think in this case federated in the AP sort of way would help much. I think this rather needs a replicated sort of implementation where if one instance goes down the same trackers live on at a different location. But I guess this would also require client support to automatically fetch a list of alias tracker locations.
Like a torrent of torrents.
