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 Jun 21, 2019. It is now read-only.
The idea is to limit a MXID from initally being able to do anything but send events/messages into a force-join room for vetting, i.e. one set in: homeserver.yaml via adding: auto_join_rooms: ["#SomeRoom:HomeServer.TLD"].
After Homeserver it is decided to grant the user unrestristricted use, the MXID may be used normally and freely join other rooms on the Homeserver, and Federated rooms if the Homeserver federates.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Originally filed under In-Band Vetting Prior to Unrestricted MXID Whitelisting and explored to no avail in [Solve In-Band Vetting with Matrix-Corporal](Created issue: devture/matrix-corporal#1).
The idea is to limit a MXID from initally being able to do anything but send events/messages into a force-join room for vetting, i.e. one set in:
homeserver.yaml
via adding:auto_join_rooms: ["#SomeRoom:HomeServer.TLD"]
.After Homeserver it is decided to grant the user unrestristricted use, the MXID may be used normally and freely join other rooms on the Homeserver, and Federated rooms if the Homeserver federates.
The text was updated successfully, but these errors were encountered: