While my knowledge of IPFS is pretty basic, this strikes me as a great use case for it.
IPFS (https://ipfs.io) is a P2P internet protocol that's made to enable a decentralized internet...I believe its goal is to supplant (or at least supplement) HTTP(S). As I said, my knowledge of IPFS is still pretty basic, but I find it fascinating and I thought it might be relevant for this application.
I am probably wrong but my understanding is that IPFS is an addressing scheme. While it can be private or peer to peer it can also be public. As an addressing scheme it continues to follow the web’s client-server model. A client-server model on the web is inherently public and anonymous.
A dedicated peer to peer system focused on privacy has no server and no third party. Instead the model is client-client without third party routing. Privacy is then achieved because connections are direct, in an application layer sense, between nodes and each node is a client running the same application in the same way. This is always confidential and never anonymous. This is achieved because there is no application layer addressing used at all, not even DNS.
Think about it more in terms of a shared disk drive on a private network mapped to a local file system address instead of a web location.
* Currently it uses IP addresses for connection, which is less than ideal.
* Currently every device is treated as a separate user.
Road map:
* I am working on a web service that will issue named accounts and digital certificates. The named accounts will identify their current IPv6 address to the account service so users need only to connect to an account which can be any IPv6 address for portability.
* Once accounts are a thing I will need to change several things on the client application. My goal in this step is to separate users from devices so that a single user can connect and manage multiple devices. That extra layer of abstraction will allow options for management, security, and convenience that are not currently available.
* I also want to enable end to end encryption for all users/devices. That is just a simple matter of public key exchange built into the already designed invitation model.
* Then I want to create a text client that supports markdown.
IPFS (https://ipfs.io) is a P2P internet protocol that's made to enable a decentralized internet...I believe its goal is to supplant (or at least supplement) HTTP(S). As I said, my knowledge of IPFS is still pretty basic, but I find it fascinating and I thought it might be relevant for this application.