Why the community needs this feature?
The experience permissions do save the user from having to accept tons of permission dialogs. However, at the recent office hours (27 Feb 2024) came up the idea to avoid the experience permissions request entirely. Because this dialog still reduces the immersion of the user. This feature aims to suggest a way where the LL experiences can be used in the current form without even a single experience request dialog.
How the feature would work?
The feature requires implementing of several parts in the viewer (and a support by the server).
The viewer will receive a new setting "Automatically accept land-scope experience permissions". By default this setting is inactive. When toggled on, the viewer will accept an experience permissions request automatically whenever an experience script sends it. Only a land-scope experience can be accepted this way.
The experience accepted automatically can be also forgotten automatically whenever the user leaves it. However, this step is optional. It also makes sense not to forget the experience, to make sure the user can find and report it, should they encounter a problem and leave the place because of this.
The address bar of the viewer will receive a special icon when the land has an experience set. This icon will be filled out when the experience is accepted (automatically or not), it will be outlined when the experience was not accepted yet (no request received yet) and grayed out when the experience was blocked by the user. Clicking this icon opens a floater with the information about the experience and especially which permissions the experience requires. The floater also allows to block the experience (when it was accepted) or unblock it when it was blocked earlier. Optionally, when it is possible to accept the experience without an incoming scripted request, the floater may allow doing this.
The experiences list (which lists all experiences the user is in) will also include the blocked experiences and display for each experience if it was accepted, if it was automatically accepted (when no auto-forgetting is implemented) and if it was blocked by the user. Optionally it may include also a list of the permissions the experience requires (I not know why this information is not there, it is good to know sometimes.)