Here's the second part of this, but not a question; rather a speculative implementation should using Bittorrent this way be feasible:
What if websites, especially ones already connected on the #Fediverse, could band together by running their own network of trackers and seeds and share the load of delivering media?
Given a lot of the media on the Fedi is already being copied from one website to another (AKA from one CDN to another), this seems like an excellent application of the tech.
Update: So far I've gotten a lot of responses, some well thought out, about why using Bittorrent this way would be slow and possibly unreliable. All true, but I'm making an assumption here: slow is a valid tradeoff for the use case I describe and only applies to large files or archives of large numbers of images (say a photo gallery).
What no one has yet done is answer my original question: Has anyone proposed or implemented using #Bittorrent instead of a #CDN to deliver media for websites?
More: This does not mean my assumption is a valid one: The tradeoff may not be in the assumption's favor. Nor am I claiming the idea is workable. But I am saying 'slow' is not a deal killer as I have proposed the use cases here.
What I'm really trying to do is determine if anyone has already put any effort into something like this, being as I am certain I'm not the first person to think of it. Because they might have already run into some insurmountable roadblock I don't know about.
@jackwilliambell I had tangential thoughts like this, basically fediverse servers should store posts on content-addressable systems like IPFS, ensure only as much redundancy as they want and reduce storage costs. If it could be done on Bittorrent instead of IPFS, all the better!
