▲ | ginking 2 days ago | ||||||||||||||||
I would say it's to reduce friction - only grant permission once, rather than every time you join a jitsi meeting. | |||||||||||||||||
▲ | morsch 2 days ago | parent [-] | ||||||||||||||||
It's not so much about the permissions (which is a browser issue) but about the config.prejoinConfig.enabled flag: usually when joining a meeting, you get an interstitial page which let's you check your webcam image and sound settings before hitting join to enter the call. This setting (passed as a request param) skips that screen. I'm not a fan, either. I'm used to the interstitial page from other services, and in fact would not expect to join a call and stream data before hitting "join". Jitsi is used in many custom solutions (which may have their own UI for getting user opt-in, like a customer hitting "Next step" in a registration wizard), I expect that's why they added it. | |||||||||||||||||
|