Shared Private Files

[matheus23]

Previous writing: https://whitepaper.fission.codes/file-system/shared

Needs some thinking about how to reconcile this with conflict resolution.

[icidasset]

Do we have any thoughts yet on a spec for the format of the softlinks (aka. symbolic links) that point to the filesystem of the sharer?

Current format:

{
  ipns: $dns_link_address,
  name: "Link name",
  privateName: $private_namefilter,
  key: $base64pad_encrypted_aes_key
}

[matheus23]

Nope, that's still TBD (see #24).

It's probably going to be mostly like that, except it won't contain the "name", and maybe there's going to be a distinction between the content key and the revision key (whether the link is giving access to all future revisions or only a single revision).

[matheus23]

Actually, shared private files in this version of the spec doesn't depend on softlinks at all. If one wants to group a bunch of things for sharing together, one can just create a directory and share that (and an application may do that on-the-fly if that should be hidden from the user).

Also, it's likely that softlinks won't be a mechanism for key management like it was the case before. I.e. we used to have keys in symlinks as you note above, but the next version will likely not have that.

Anyway. I other news, the spec was just merged, so we can close this :)