Locked down demo mvp

[mikemorran]

Implementing time-boxed version of simplified demo UI to be released internally. This feature does the following for any hub_id specified as demo room in the admin panel...

• Bypass profile setup step of entry flow (avatar and display name selection)
• Force individual profile settings for default avatar, random name generation, and always hide nametag
• Disable UI elements for...

1. Presence Log when new users enter and leave
2. Chat button
3. Share button
4. Place button
5. Microphone button
6. Object Menu
7. People Menu hover and clickability
8. "Change Name and Avatar" in the more menu

• Disable "T" and "/" hotkeys which open chat
• Prevent separate tab avatar changes with avatar.js

Public release of this feature will occur once room info and settings for a demo room can be programmatically specified in the admin panel. Also, additional edit should be implemented to support an array of demo room hub_ids.

Specific Feedback Requested:
@keianhzo I was unable to solve checking for canVoiceChat before our hack to request mic when using Safari. This is because the hack requests permissions before we ask reticulum for the hub_id or preferences. Any input on why we request mic permissions so early?

@keianhzo I implemented a pretty sloppy hack in store.js to prevent users from updating their avatarId from separate tabs using the avatar.js panel. Any thoughts about how this could be better accomplished, especially since it is using AFRAME?

@nikk15 @nickgrato Any thoughts on how I removed pointer-events on the People Menu in ui-root.js, src/react-components/room/ContentMenu.js, and src/react-components/room/ContentMenu.scss? Could this be improved?

[nikk15]

I think installing the Prettier extension in VSCode should solve some of the linting issues too. I have my VSCode settings set to "format on save" :)

[keianhzo]

This is close to be ready. I have left a few comments, let me know if you need more context.

@keianhzo I was unable to solve checking for canVoiceChat before our hack to request mic when using Safari. This is because the hack requests permissions before we ask reticulum for the hub_id or preferences. Any input on why we request mic permissions so early?

Yeah, it's unfortunate that we still need to do this. It might have been already fixed and we can maybe remove it. I'll test. For this PR I think it's ok to leave it as it is, we can remove it in a follow-up in case it's not necessary anymore.

@keianhzo I implemented a pretty sloppy hack in store.js to prevent users from updating their avatarId from separate tabs using the avatar.js panel. Any thoughts about how this could be better accomplished, especially since it is using AFRAME?

Do we want to let the user choose an avatar during entry? If we don't care about that we can maybe switch this to:

    if (isLockedDownDemoRoom()) {
      return;
    }

Otherwise you can avoid using the AFRAME symbol by using:

if (
      newState.profile !== undefined &&
      newState.profile.avatarId !== undefined &&
      isLockedDownDemoRoom() &&
      APP.scene.is("entered")
    ) {
      return;
    }

We need to migrate that check at some point so it's ok to use that.

[mikemorran]

@keianhzo Re: hack to prevent avatar selection in a separate tab.

I am attempting to allow default avatar selection on initial connection, not avatar selection in the entry flow, before disabling any avatar changes. This is important to force all users joining a demo room to choose from a default avatar and not bring in an avatar from their previous session in a different room. Since avatar.js does not specify that avatarID was changed in a separate tab, I am doing this weird hack to only allow avatarID changes on initial connection to a demo room (hence trying to judge when the scene is loaded). Happy to discuss further!

[mikemorran]

Feedback implemented!

[mikemorran]

I think installing the Prettier extension in VSCode should solve some of the linting issues too. I have my VSCode settings set to "format on save" :)

Implemented

[mikemorran]

Re-opening accidental close

Changed implemented!

[keianhzo]

I've made a couple more suggestion to try to minimize the changes impact. I think after this we should be good to go!

[keianhzo]

I think when we remove those two asycs that were left we are good.

[keianhzo]

Nice! this looks ready to ship after a QA pass.