Skip to content
This repository has been archived by the owner on Jun 21, 2019. It is now read-only.

Solve In-Band Vetting with Matrix Policy Gateway #3

Open
MilkManzJourDaddy opened this issue Aug 30, 2018 · 0 comments
Open

Solve In-Band Vetting with Matrix Policy Gateway #3

MilkManzJourDaddy opened this issue Aug 30, 2018 · 0 comments

Comments

@MilkManzJourDaddy
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant