-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kick / Ban #38
Comments
This might require a change to mosquitto itself Mosquitto comes with two functions that might facilitate this for plugins:
The latter is used only by the dynamic security plugin (more docs) which may likely pose a compatibility issue w/ |
I like that plugin! It's probably one of cleanest ways to do this, but you're right it will take time to look into integrating both plugins. I'm working on sending a message that will convince the client to logout. |
Kick implemented for Owners and Editors: arenaxr/arena-web-core#284. |
To implement Ban, it'll take a few more days. Essentially, we add to the user database Scene Permissions a Banned Users list. I think the right way to do this is to use the REST GET/PUT operations of the scene permissions table from the main scene Chat JavaScript. However, it looks like the default ManyToManyField used for Editor/Banned lists in the database exports the user list enumerated key ID rather than the username, which the website cannot use. So some work to enable GET/PUT operations to use the usernames rather than enumerated keys is needed. |
Progress:
|
Remove User confirm could have 5 options in increasing severity, each one including properties of the former:
|
Try to integrate Jitsi conference controls where possible:
|
Similar in many other platforms, the owner of a room and kick / ban people from the scene. While I know this might be difficult, I propose a program that stops a user (by user name) from moving, talking, chatting, video, etc (simply freezing them out). I feel as though the sheer boredom might detour someone from doing something stupid.
The text was updated successfully, but these errors were encountered: