You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2024. It is now read-only.
Is your feature request related to a problem? Please describe.
Roles currently allow individuals to control remote audio and video settings. However, they do not allow a role to control a remove user's screenshare. It looks like the demo application uses a custom event workaround as seen here:
Yes, there is one downside. Unlike audio permissions that are controlled on a role basis, now, technically any role can emit this event and stop anyone's video.
While it's unlikely given my use case for this to be abused, the current implementation is very much a workaround.
Also, when first implementing 100ms, it's odd to see APIs support av controls:
Is your feature request related to a problem? Please describe.
Roles currently allow individuals to control remote audio and video settings. However, they do not allow a role to control a remove user's screenshare. It looks like the demo application uses a custom event workaround as seen here:
https://github.com/100mslive/100ms-web/blob/f67d7aabf39595234a8f60a96becb874250104ce/src/plugins/RemoteStopScreenshare.jsx
Describe the solution you'd like
It would be great if this was a top-level feature just like muting a remote peers audio/video
Describe alternatives you've considered
I could use the custom event method.
The text was updated successfully, but these errors were encountered: