User specific files: E.g., for SharedImages discussion thread read state.

[crspybits]

After talking to Dany, we figured out a way to do this: The file could be marked in the file index table on the server as downloadable/visible only by a single user-- When everyone else does a file index, they don't see this file. When the user in question does a file index, they see this file.

This could be used for user-specific settings that an application wants to save-- e.g., the read state of specific discussion threads. This would enable that read state to be preserved, even if the app was deleted and reinstalled. And would enable that read state to be used on a different device, by the same user.

[crspybits]

An alternate way to handle this is to keep the unread counts in either the discussion thread file itself, or in a new file (one per image file). This would mean that there would be an increase in the number of downloads per user. A download would be incurred each time a discussion would be read. I would have to also change the way the progress indicator behaved-- having to see these downloads would not make for good UX.

A main difference between the two options: either private or shared unread counts is-- do we want other users to know whether or not someone read a message?

[crspybits]

User specific files could also enable periodic storage of an index.html file that would let the user navigate cloud storage files, should they no longer want to use the app.

[crspybits]

I just had a thought. This problem may be fairly easily solved once I get the full setup with multiple sharing groups. aka. Albums. If I create a self-only sharing group when a user is created, it could serve this kind of purpose. As long as no one else ever gets invited to the sharing group, it should enable transfer of only self-related state between a users devices.