Skip to content

MSC4494: Membership-based invite blocking#4494

Open
timedoutuk wants to merge 1 commit into
matrix-org:mainfrom
timedoutuk:timedoutuk/mutual-rooms-invite-filter
Open

MSC4494: Membership-based invite blocking#4494
timedoutuk wants to merge 1 commit into
matrix-org:mainfrom
timedoutuk:timedoutuk/mutual-rooms-invite-filter

Conversation

@timedoutuk

@timedoutuk timedoutuk commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Signed-off-by: timedout <git@nexy7574.co.uk>
@turt2live turt2live added proposal A matrix spec change proposal. Process state. A-Client Server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. A-Safety labels Jun 25, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation requirements:

  • Client (setting)
  • Client (using)
  • Server (respecting)
  • Backwards compatibility testing


A new `default_action` for `m.invite_permission_config` is introduced: `deny_public`.

`deny_public` is intended to prevent invites being sent by users who only share public rooms with

@Half-Shot Half-Shot Jun 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just for avoidance of doubt here: Inviters won't be able to invite you if they don't share a room at all?

I'm wondering really if this is more like "allow_private", as the proposal is really stating allow invites IF they come from a private source. (Albeit, we've complained in the past about using private in the spec and it not really having a defined meaning)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is something I went back and forth on while drafting. As far as I'm concerned, receiving an invite from anyone you don't share a non-public room with counts as a "public"-sourced invite, because they could've just found your user ID online (public) or in some other public room.
I'd like to keep that functionality in this proposal in some form, but if you think it'd be better split into another action value I'd be open for that too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Client Server Client-Server API A-Safety kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal. Process state.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants