BitTorrent protocol extension proposals 17 and 19 describe a problem and possible solution that I'd like us to take a look at for Ara as well:
Many websites that list a BitTorrent download also provide a HTTP or FTP URL for the same file. The files are identical. A WebSeeding BitTorrent client can download from either source, putting all the parts together into one complete file. The HTTP or FTP server acts as a permanently unchoked seed.
The user flow for a creator on Ara could be something like this:
Creator uses FM on laptop to publish a folder
FM gives creator an encrypted .tar.gz to upload but not link to their Wordpress/SquareSpace/any website
Creator pastes HTTP link to where they uploaded the file back into FM
✨ (new stuff happens under the hood) ✨
Creator posts ara link to Twitter, then promptly closes laptop lid and leaves coffee shop
Fan clicks tweeted link, gets FM, buys Creator's work, and FM downloads and decrypts it from HTTP seed (because there are no other seeds available yet)
BitTorrent protocol extension proposals 17 and 19 describe a problem and possible solution that I'd like us to take a look at for Ara as well:
Many websites that list a BitTorrent download also provide a HTTP or FTP URL for the same file. The files are identical. A WebSeeding BitTorrent client can download from either source, putting all the parts together into one complete file. The HTTP or FTP server acts as a permanently unchoked seed.
https://www.bittorrent.org/beps/bep_0017.html http://www.bittorrent.org/beps/bep_0019.html
The user flow for a creator on Ara could be something like this: