09-12-2023, 03:43 PM
I'm not sure if you are concerned about musicians synchronizing to a folder they shouldn't be able to modify, but you can control that with the read/write privileges on the folders. So that would take care of that, if that's an issue for you.
As far as keeping parts secure, I don't really have anything in place right now to restrict the sharing of parts, or prevent users from restoring a library backup with parts they shouldn't have access to, or anything of that sort. That starts venturing into a realm where one of a few things has to happen:
1) User accounts could be added to uniquely identify a user to understand what things they should have access to (which requires a ton of backend stuff). This is my least favorite approach.
2) An option would have to be added to password protect songs, preventing sharing or modification until the password is entered
3) File storage would have to be locked down hard to prevent users from having direct access to their files, as there is no way to prevent them from just copying the file out of the storage location otherwise. This kind of goes against the benefits of using Android though, and I imagine many users would not like this.
4) A new custom file type has to be supported that is a modification of a standard PDF to include permission information for what users can access the file, and how many times, if any, it should be allowed to be shared, and by which users.
I'm not really sure what is the best solution for this. I'm open to hearing other ideas as well. I know some users have asked for an option to make a song "read-only", but unless it's password protected, it would still be easy enough for a user to make the song writeable again if they just toggled off the read-only setting.
Mike
As far as keeping parts secure, I don't really have anything in place right now to restrict the sharing of parts, or prevent users from restoring a library backup with parts they shouldn't have access to, or anything of that sort. That starts venturing into a realm where one of a few things has to happen:
1) User accounts could be added to uniquely identify a user to understand what things they should have access to (which requires a ton of backend stuff). This is my least favorite approach.
2) An option would have to be added to password protect songs, preventing sharing or modification until the password is entered
3) File storage would have to be locked down hard to prevent users from having direct access to their files, as there is no way to prevent them from just copying the file out of the storage location otherwise. This kind of goes against the benefits of using Android though, and I imagine many users would not like this.
4) A new custom file type has to be supported that is a modification of a standard PDF to include permission information for what users can access the file, and how many times, if any, it should be allowed to be shared, and by which users.
I'm not really sure what is the best solution for this. I'm open to hearing other ideas as well. I know some users have asked for an option to make a song "read-only", but unless it's password protected, it would still be easy enough for a user to make the song writeable again if they just toggled off the read-only setting.
Mike