3 ms·
Great stuff, and maybe also a step towards a content-centric web, which is indifferent about where content comes from, only that it's precisely what the audienc
by gojomo 15y ago
Great stuff, and maybe also a step towards a content-centric web, which is indifferent about where content comes from, only that it's precisely what the audience requested.
Though WebRTC might be the 'right', standards-based way for peer-to-peer web communications, I'd be wary of depending on it arriving, with the right features, in any necessary time frame. Incumbent-organization standards efforts often don't deliver with the boldness and promptness that edge innovation needs.
Maybe you'll need to give (some subset of) users a plug-in or node.js daemon, that runs alongside their browser as a connectivity hack-around, in the meantime. Aesthetically impure, yes, but such compromises are another kind of 'schlepping' that sometimes enables breakaway project success.
- sirclueless 15y agoI'm not sure I follow. This new service requires cooperation with a specific browser on the other end of a centralized service in order to get any content at all. Compared to a uniform resource locator on top of a dynamic, distributed naming system connected by a robust, global packet-switching network, I'd say this new system is way less "content-centric" and way more sensitive to the content's source.
- gojomo 15y agoYou're right; I'm projecting my own hopes about what a pure-JS, all-in-browser peer-to-peer sharing stack could do, rather than considering just the specifics of this quick-and-dirty shared folder approach (which isn't even yet p2p, though that's clearly the hope). Once the remaining browser pieces are in place (via either WebRTC or another shim), a content-centric DHT beyond just shared folders could be the next step. You could have "trackerless torrenting in a tab". Or even "Tor-in-a-tab".