One of the things holding back the adoption of Twister even though it has a superior underlying architecture is the lack of ability to post content. Specifically the ability to put a picture in your post. i realize that this have been debated previously concerning the way perhaps magnet links could be integrated.
Instead, I propose that there be a modular integration of an existing solution.
Adding IPFS (
http://ipfs.io/)(https://github.com/ipfs) support to only the HTML client would allow for the presentation of media with a simple hash location. IPFS works as single BitTorrent swarm, exchanging objects within one Git repository. Since IPFS uses public and private key cryptography deeper integration could be done, but a simple addition to the HTLM client as method to "pin" or "favorite" content could propagate media with no strain on the twister network. There is even a open source JS player (
https://github.com/ipfs/examples/tree/master/webapps/play) available. If this were added to the client you would have a drop-in replacement for youtube literally overnight. Ive been testing over the weekend and it is a simple and FAST way to publish distributed content, it just lacks a way to index and share content easily. Which is exactly what Twister is.