4 ms·

I'm especially interested in the "self-authenticated DNS". I think a lack of accessible p2p name system is the biggest hangups for a P2P web. People are overl

I'm especially interested in the "self-authenticated DNS". I think a lack of accessible p2p name system is the biggest hangups for a P2P web. People are overly dependent proprietary namespaces (Facebook, ICANN, Google, etc.) for making connection. For example, there are many applications I could see myself using locally, in human presence, over LAN. e.g. music studio MIDI/control sharing, real-time document collaboration and drawing, audio mixing, games... Serving such applications might be as easy installing them on a local copy of sandstorm.io, or even double clicking an app or installing a .deb package. But the hard part is finding stable, humane ways to make connection between the machines without relying on an external network. It really perplexes me that after all these years, ordinary LAN file sharing is still one of the most unreliable things to do with computers/phones.

greenyouse 10y ago
Isn't this a problem that people solve using overlay networks[1]? Most P2P systems use things like DHTs to relate IP addresses to the overlay network's addressing protocol so encrypted routing can be done over the internet. It shouldn't be too hard to self host a service but the caveat is that you'd have to access it through whatever P2P network you choose. As an example, it'd be easy to host your own services through a Tor hidden site or I2P. I don't know much about how sandstorm works but things like a git server should be easy to host over P2P. The bandwidth over Tor and others can be really slow but some P2P protocols have high bandwidth[2]. [1] https://en.wikipedia.org/wiki/Overlay_network https://en.wikipedia.org/wiki/Overlay_network [2] https://code.google.com/archive/p/phantom/ https://code.google.com/archive/p/phantom/