Eureka? Node-webkit + bittorent == censorship resistant web-app platform
> The Net interprets censorship as damage and routes around it
With that in mind, what if somebody were to create a simple cross-platform application shell based on node-webkit with a Javascript Torrent Client integrated, and just one input box that a user would paste a magnet link / Torrent Hash into?
The application would then resolve the info hash back into a magnet link, connect to the Torrent Network and download the new application payload.
After the download is done, reload the shell application with the newly downloaded payload as init target, and voila, you're running the application. As long as there are seeds in the network, anybody would have access to the application and it can never be taken down.
A simple extension to the package.json format already used in node-webkit based applications could include screenshots and stuff directly embedded inside the torrent and show the user a preview of what they're downloading (these would be downloaded first by the shell)
No domains to block, no repositories to block, and all the power of the BitTorrent network for peer to peer distribution.
Tell me what you think, I'll prototype it if i'm not completely missing something very important.
These replicas don't need to be CouchDB instances, they just need to speak its protocol. Fortunately for you there's an excellent package that does that: PouchDB (http://pouchdb.com/), which you can use as a library (so you don't need to install another server) in your node.js application.
Finally, when the user wants to install the application that is published on the npm registry, it would have to get some kind of signature from the registry, and then pick any mirror to download the content from. This is a very important step: there must be a way for the user to make sure what he downloads is legit. One can assume if it's on the npm registry then it is.
This is not bittorrent, but it's much more integrated in the current environment which means less hacking to do.
The main driving thought about this is making sure that outlawed/censored software can be accessed via an unblockable channel wether it's been banned or not.
Integrity verification is a good point, the shell application could do something with that possibily (verifying crc / a pgp hash somehow perhaps)
> As long as there are seeds in the network
There's one problem. Like all other P2P, when people find it not interesting, they stop seeding and it will naturally die.
> all the power of the BitTorrent network for peer to peer distribution
How does the application determine who's the single source of truth?
> No domains to block, no repositories to block
But how does one discover the hash/magnet link? Search over P2P I guess?
> node-webkit with a Javascript Torrent Client integrated
One can craft a program, a special browser like Tor Browser using C++ or something. Any particular reason why JS?
Just my 2 cents. I find the idea interesting yet needs polish.
That's true, this idea works best when people actually want to access the program
> How does the application determine who's the single source of truth?
Just by inputting the torrent itself. If the torrent changes, so does the magnet hash
> But how does one discover the hash/magnet link? Search over P2P I guess?
Hashes can be distributed by any means already available: facebook,twitter,websites, pen and paper, etc.
> One can craft a program, a special browser like Tor Browser using C++ or something. Any particular reason why JS?
Not particularly, mostly ease-of-use and cross-platform abilities readily available. This same idea can work on any stack ofcourse
> Just my 2 cents. I find the idea interesting yet needs polish.
Thanks, that was why I came here :)