3 ms·
Question: why did noone extend the torrent protocol to understand http[s] and speak to servers that support resume? edit: I’m just now reading https://www.bitt
by joshspankit 6y ago
Question: why did noone extend the torrent protocol to understand http[s] and speak to servers that support resume?
edit: I’m just now reading https://www.bittorrent.org/beps/bep_0019.html https://www.bittorrent.org/beps/bep_0019.html and that’s exactly what they did. My bad
- ajconway 6y agoIt is supported, it’s called web seeding.
- black_puppydog 6y agoalthough from how I understood it, web seeding really assumes you can control the folder structure on the servers. so you can't just curated a data collection from publicly accessible sources and freely map torrent contents to files on http for bootstrapping/reliability. too bad, really. it seems like a cool thing to just make a torrent from e.g. public datasets that are hosted on flimsy university servers. make the torrent, distribute it, the swarm keeps the files available and reduces load on the university servers, and the server keeps the torrent from dying even if the dataset is niche.
- crest 6y agoThere are two BEPs for web seeding. One is defined in terms of base URL and relative paths the other in terms of pieces and offsets into them. Few clients implement both web seeding protocol extensions.
- joshspankit 6y agoCheck out https://www.bittorrent.org/beps/bep_0019.html https://www.bittorrent.org/beps/bep_0019.html