Feature Request: Permission system

[eanders-ms]

Permission to access voice, to teleport user to location or another space. etc. TBD

[willneedit]

Possible:

• Access user's microphone
• Access user's HMD camera (mixed reality devices)
• Access unique User ID (per-app base mandatory, no blanket on/off switch)
• Access user's friend list
• Alter the user's appearance (attachments)
• Move the user (translation, rotation) / teleport the user (across spaces)

Implementation notice:
Problem: Many mobile app developers simply let their applications crash or exit if the permissions they wanted - even permissions not essential for the core functionality of their apps - are not granted, removing the element of choice from the user.

Suggestion: The permission settings remain invisible to the MRE; it shall never know if a given permission is granted or not. Affected functions will return a success even on denied permissions, but return 'empty' data sets, like an empty friend list when the user denied access to it, or a silent audio channel like a muted microphone if mic access has been denied.

[eanders-ms]

Additional permissions to consider:

• Permission to attach objects to the user
  • Attachments are vector for griefing
• Permission to let the app know about the user at all
• Permission to read the user's position
• Permission to write the user's position (teleport to another position in the space)

Also it would be nice to have a MRE Permissions panel, where the user could manage permissions across all MREs in the space. This could be a tab on the settings screen.

[eanders-ms]

Reference #606