question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Restrict the rooms a guest can join

See original GitHub issue

The GNOME community would like to be a good citizen in the Matrix universe, and not be an entrypoint for spam to other instances/room. To do so, we will restrict registration, but we would love to open guest accounts instead. The main blocker is we can’t prevent guest accounts from spamming other instances.

Since rooms don’t belong to a single server but are distributed in the Matrix universe, it’s not possible to develop a feature like “guest accounts should not be able to leave the server”. An flexible way to achieve what we want would be to allow guest accounts to join rooms only if there already is a :gnome.org alias bound to this room at the moment when they are trying to join. A less flexible (but maybe simpler?) way to do it would be to implement a room allow-list in homeserver.yaml. Per my understanding, this is something the homeserver of the guest account needs to enforce and doesn’t require a specific MSC for that.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:2
  • Comments:12 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
baboliviercommented, Oct 4, 2021

It might be worth reevaluating this now that spaces are a thing, and sound like an interesting way to make this feature happen.

1reaction
callahadcommented, Jun 17, 2021

In the general case, it seems like this may be sufficiently addressed by the permissions of rooms themselves, which can specify whether or not guest accounts are allowed to join. This empowers room admins to choose a degree of openness/moderation that they’re comfortable with. In Gnome’s specific case, perhaps a custom spam checker module could be used to restrict specific actions at the homeserver level.

The Synapse team would be willing to evaluate a patch which prevented guests from initiating joins over federation, but we’ve not thought though the issue sufficiently to say whether or not we would merge it a priori.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Change participant settings for a Teams meeting
Go to Meeting options. You can access this page a few different ways, depending on what kind of meeting it is. Scheduled meetings....
Read more >
How to Keep Uninvited Guests Out of Your Zoom Meeting
When you disable “Join before host” in your settings, a Waiting Room will automatically greet your guests until you've started the meeting.
Read more >
How to Reserve a Hotel Room Block for Your Wedding
Once you set up a wedding room block, most hotels will give you a web link to share with your guests so they...
Read more >
Managing Access to Your Adobe Connect Room
The third option is the default and it provides a nice balance between keeping access limited, while giving the host the option of...
Read more >
Setting up “No arrivals” and “No departures” restrictions
Find the room you'd like to set the restriction for, then click the drop-down arrow next to the room rate to see all...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found