Hello everyone,
I recently came across an article on TorrentFreak about the BitTorrent protocol and found myself wondering if it has remained relevant in today’s digital landscape. Given the rapid advancements in technology, I was curious to know if BitTorrent has been surpassed by a more efficient protocol, or if it continues to hold its ground (like I2P?).
Thank you for your insights!
A better question is, what would you improve over current way that torrents work.
I wish there were some way to enable availability to persist even when torrents’ peak of popularity has passed - some kind of decentralized, self-healing archive where a torrent’s minimal presence on the network was maintained. Old torrents then could become slow but the archival system would prevent them being lost completely, while distributing storage efficiently. Maybe this isn’t practical in terms of storage, but the tendency of bittorrent to lose older content can be frustrating.
I don’t see what you can do at the protocol level to improve availability, you still need people storing the file and acting as peers. Some trackers try to improve that by incentivizing long term seeding.
It’s called private trackers, and they are great.
Make mutable torrents possible.
What’s the advantage to that? I don’t want the torrent I’m downloading to change.
I want that. For example you downloaded debian iso version 13 and after some time it can be updated to 13.1. Obviously it shouldn’t be an automatic operation unless you allowed it before starting download.
I wouldn’t call that mutable, more like version tracking in which each torrent is aware of future versions.
I kind of like that, but you might be able to accomplish it with a plugin or something.
Put a file in the torrent called “versions” or something like that, and in there would be a url that the client can use to tell you if there is a new version.
It wouldn’t change the protocol though, since the new version and old version would still need to be separate entities with different data and different seeding.
Like the 13.1 torrent being only a patch to the 13 one and listing it as a dependency? Downloading the 13.1 torrent would transparently download the 13 if it wasn’t already, then download the 13.1 patch and apply it. But I don’t think any of this needs to be at the protocole level, that’s client functionality.
Resilio sync can do this, I’m pretty sure.
Although if implemented as an extension to BitTorrent, I’d want it to be append-only, because I don’t want to lose 1.0 just because 1.1 becomes available.
The last 0.01 percent comes in at the same speed as the rest of it