-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Join passwords (SPEC-61) #51
Comments
Jira watchers: @erikjohnston @kegsay @leonerd @ara4n |
I don't think this is needed for the bot, though it might be easier than changing the bot. So long as the bot gets invited to the room, then it should technically be able to invite the ghost users just before they join. |
I agree that this shouldn't be needed for the bot. The IRC bot is always in the room right? Why can't it invite people before it blindly joins them? -- @kegsay |
(Though I think it would be a cool feature to have) |
We need this for parity with IRC when IRC bridging. -- @ara4n |
Any chance of getting this triaged? This is a pretty glaring omission for the IRC bridge. -- Håvard Pedersen |
My biggest question is who stores the secret and where? It could be in a state event, but that means clients can read it (not sure if it’s a problem, but definitely not how IRC works). |
Some people at Matrix Finland are missing room keys for native Matrix rooms for purpose of letting new users join native rooms without having to ask any specific person for access or having to knock. If this happens, I hope it will be mergeable with knock_restricted (or the more sophisciated join rule which that one is waiting for). (Other keywords: room passwords / channel keys / channel passwords) |
AKA "join keys" on IRC. The idea that anyone can join an invite-only room if they present some shared secret.
Wanted because Matrix Internal is now invite-only, meaning the Matrix<->IRC bridge bot can no longer join, nor have its ghosts join the room.
(Imported from https://matrix.org/jira/browse/SPEC-61)
(Reported by @leonerd)
The text was updated successfully, but these errors were encountered: