> The first step is designing your data to be stored in files, rather than a database
Somewhere in the middle-- ipfs gives you native access to the merkledag datastructure, so you can actually port most databases to using ipfs as a kv-store directly. (think an embedded sqlite or something). and on the other side, maybe you dont need a database. maybe you can just construct the graph of objects you need and write that to ipfs.
> maybe becoming "friends" with another user involves a key exchange?
yep! we've discussed an `ipfs friend` cmd
> Ultimately I think IPFS is a pretty cool concept, one I've kicked around a bit but never fleshed out. Major kudos to Juan and everyone else for taking it on - I look forward to seeing where this goes.
Somewhere in the middle-- ipfs gives you native access to the merkledag datastructure, so you can actually port most databases to using ipfs as a kv-store directly. (think an embedded sqlite or something). and on the other side, maybe you dont need a database. maybe you can just construct the graph of objects you need and write that to ipfs.
> maybe becoming "friends" with another user involves a key exchange?
yep! we've discussed an `ipfs friend` cmd
> Ultimately I think IPFS is a pretty cool concept, one I've kicked around a bit but never fleshed out. Major kudos to Juan and everyone else for taking it on - I look forward to seeing where this goes.
Thank you!! Come help us build it! :)