Today’s reddit post on AWS dropping support on BitTorrent made me think that maybe it would be a good (if low priority) idea to make it possible for Storj to act as a bittorrent webseed.
For those not familiar with bittorrents, this is a technology that allows distributing data in a true p2p fashion, where every client who has even small bits of a distributed file can share them with other clients. Usually all clients wanting to retrieve a specific distributed file simply get them from other torrent clients who have it. To initiate distribution, one just runs the first client with all the data. Webseeds is an alternative, where in case there are no torrent clients having all the pieces, data can be obtained by http using some external hosting prepared by the person initiating distribution.
AWS S3 used to have a feature where you could mark any file as one to be also distributed by torrents. This feature was supposed to lower the costs to share popular files, as most of the traffic was p2p torrent traffic, and not egress from S3.
Regarding Storj, I’d imagine the following features:
- Basic: building a webseed support into some popular bittorrent clients, so that people already using bittorrent could have an alternative way to fetch data.
- A bit more complex: building a (specialized Storj-only) torrent client into libuplink, so that the torrent feature would work transparently for the customers.
Especially the latter could then be used by customers to, let say, have a local copy of their Storj-stored data for faster/cheaper access, transparently without leaving libuplink.
Just a shower thought.