This will be a very non technical post but please bare with me.
Here is the theoretical situation.
•The first user uploads a list of files to app (pays for PUTS)
•The app will store these files in its database
•The app scans the second users files before upload, against its DB to see if the files already exist to avoid the PUT cost of like files while still uploading novel files to DB (and on and on)
•When a new user has a file that already exists in the DB they are given access to the file without having to upload.
•The original uploader should have permission to the file to edit the name if they like (not the file just the file name)
•Users who were given access to a like file should also have permission to edit the files name too
•What kind of permission would the app need to achieve this?
•Can these files be shared between users?
•Upon initial upload should these files be public?? (Currently they are stored in a container that is encrypted by default)
•Obviously this a mutable data type but by the sounds of it, shared mutable data is more for sharing one users data between multiple apps not multiple users
•If one user changes the name of the file is that reflected across all users? (Not good) assuming the name is uploaded in the same MD as the data. I need to dig a bit and find out if this is the case in my situation.
Not trying to make others do the hard work for me I’m just out of my depth a bit here. I am currently reading but either way I think these answers could be helpful to more than just me. If this all works out I think it has pretty big implications not just for the use case I have in mind but for so so many more.