Add support for decentralized storage

[scottveirs]

In yesterday's standup, motivated by expiration of AWS and Azure credits this year, we had a lively discussion of potentially shifting to decentralized storage of Orcasound audio data. This could initially happen for just compressed, lossy bouts for human listening -- aka a playlist of Greatest Hits of Orcasound. But it might some day also be a cost-effective and secure solution for the full streaming archive, currently about 3.5 TB or 250MB/node/year for only HLS data. (Here is a calculator for estimating data storage costs within AWS S3 for Orcasound).

Here are some related follow-up links that @prafulfillment offered in the Orcasound Slack:

• https://opendata.stackexchange.com/questions/4080/what-are-some-opendata-torrents-to-seed
• difference between IPFS & Torrents. TL;DR — IPFS can share a massive dataset with peers accessing only small parts whereas BitTorrent needs the entire library downloaded to swarm (at least from the comments)
• #208 Comparison of IPFS and BitTorrent for Archives
• how to from Wikimedia Foundation: https://github.com/ipfs/distributed-wikipedia-mirror