3 ms·

> This would be IPV6 based (lots of available addresses) and end to end encrypted. FYI Yggdrasil https://yggdrasil-network.github.io/ https://yggdrasil-network

> This would be IPV6 based (lots of available addresses) and end to end encrypted. FYI Yggdrasil https://yggdrasil-network.github.io/ https://yggdrasil-network.github.io/ already gives you a unique, stable IPv6 with mesh layer encryption for your packets. Likewise a DHT for "subreddit" or topic identity (or even a blockchain for that as naming is one of the few things that can be solved with a blockchain, though as always there are tradeoffs) shouldn't be too hard to build as a lot of the ingredients (Kademlia, GNS, IPFS, IPNS, etc) already exist. I suspect the hardest part will be building the product experience around this whole system. The tech is mostly there. But if you want to enable non-technical people to use it, you have to make the system simple and clear to use, which a lot of technical people (myself included) struggle with.

ChuckMcM 3y ago
> I suspect the hardest part will be building the product experience around this whole system. I think this is exactly right. Not surprisingly, I wrote up a business plan for this can called out this point. The approach I have advocated in the plan was to appliancize the end node to minimize the back end configuration. Having done this at FreeGate and NetApp I definitely saw the benefit of "install this box, turn it on, and now you have access to this service." as a huge win, both for adoption and for support. The key then is you install the app, or apt-get the application and securely attach with a button press on the local network. Pick a handle to give to your friends and you're off to the races. Most of the business plan was around the economics of an open protocol and the ability to make money selling the service installed in a ready-made platform (selling software wrapped in hardware) ala current NAS offerings. Good returns on growth, less so on saturation.

ChuckMcM 3y ago

> I suspect the hardest part will be building the product experience around this whole system. I think this is exactly right. Not surprisingly, I wrote up a business plan for this can called out this point. The approach I have advocated in the plan was to appliancize the end node to minimize the back end configuration. Having done this at FreeGate and NetApp I definitely saw the benefit of "install this box, turn it on, and now you have access to this service." as a huge win, both for adoption and for support. The key then is you install the app, or apt-get the application and securely attach with a button press on the local network. Pick a handle to give to your friends and you're off to the races. Most of the business plan was around the economics of an open protocol and the ability to make money selling the service installed in a ready-made platform (selling software wrapped in hardware) ala current NAS offerings. Good returns on growth, less so on saturation.