Apps data under IPNS

[Kubuxu]

To prevent possible clutches and make it still possible to use IPNS directly I propose that apps using IPNS should make one directory in the IPNS root and make it hidden (prefix it with .).

This way user won't always see those directories and we don't risking case when user wants to create directory of this name manually.

Also those directories should be named uniquely, by using descriptive names, not like.boards or .messages, so we don't have to fight in case of collision.

[fazo96]

my app is using a folder named ipfs-boards-profile. Will probably never collide with anything else, but it's not hidden because it is readable enough with a simple file manager in my opinion.

I don't fully agree with making the directories hidden, I think users should have a clear look at what they're publishing. I'm open to suggestions though :)

[hackergrrl]

If each app had its own keypair, the hash of the public key could be used as the directory name: this guarantees uniqueness, and associates the app with its data.

[Kubuxu]

@fazo96 Users can have clear look into apps directories but they don't have to see them at all tiles. This is why hidden directories were created, same way you have applications directories in your home directory.

Imagine finding your own, manually created directory when there are 50 auto-generated ones. They can be hidden as they will be hardly ever used manually.

[fazo96]

uhm, we need to handle this in POST or an extension of it I think.

@noffle that idea is quite cool! :+1: but what would the private and public keys represent? An identity? Identity is a big deal, and very hard to get right

@Kubuxu I guess you are right. This should be handled in POST (or an extension of it), no draft for the protocol has started yet. Maybe we can start a rough draft since @jbenet is busy in new zealand and will also be busy working on go-ipfs.