Pinning/Unpinning Policies

[aschmahmann]

Not related to the spec itself, but something to consider in terms of what functionality we need.

It's fairly easy to reason about the API when it's triggered by user actions like a CLI command or a UI operation. However, there's been requests for pinning "policies" such as "remotely pin MFS files" or "remotely pin all locally pinned files". In the case of these policies it's less clear what happens in an automated setting. For example, a user has two machines A and B:

1. A pins cid C
2. B unpins C
3. How does the pinning service know if the pin or unpin happened first?

Perhaps if we could track the latest "state" of the pinset in clients then they would be able to update their local understanding of what's pinned on the service provider before allowing the clients to send an "unpin" command.

[Gozala]

I think there is some overlap between this and #7 issue. On the policies side one thing I have being wondering is what happens when some content in MFS is edited / deleted. Is previously pinned content going to get unpinned ? I imagine user wanting to keep that around as a backup. Which gets us into for how long do you want keep such backup and how much of it also relevant question.