-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
if all users leave a room, the room should not wink out of existence. (SPEC-211) #95
Comments
Jira watchers: @ara4n |
Links exported from Jira: duplicates SPEC-147 |
The idea of letting ASes participate in a room without explicitly joining is finally specced in https://github.com/matrix-org/matrix-doc/issues/544 -- @ara4n |
Could SPEC-216 help with this? If the act of leaving a room doesn't actually part the user from it entirely, can these 'left' users keep the room alive? Only if the users explicitly discard the room and its history (as per SPEC-224) would the server stop participating - and if all the users discarded it the room would wink out of existence, which is probably what's wanted in that instance. -- @ara4n |
I'm assuming this is the same thing, but if someone can check: rgh Matthew (@matthew:matrix.org) rgh rgh -- @ara4n |
One can probably live with 1, but 2 is really annoying. -- Alien A |
We’re currently searching for an alternative to XMPP at our company, and I suggested Matrix as I’m using it personally and I am very satisfied. A sysadmin from our company launched a Synapse test server and asked me to join. We chatted a little with the default client provided by Synapse (Matrix Console Web). He did several leave/rejoin tests and was at first happy to see that the history was preserved. Then he kicked me out of the room and left the room himself. We were now unable to rejoin the room or to recreate the room with the same alias. He was directly put off because of this and stopped considering Matrix as a possible solution. :( For invite-only rooms, it makes sense of course, but this is also the case for public rooms. Even though users should normally not leave a room if they want to keep its history (they stay in the room even when not connected), I think this issue is a serious barrier for people testing out Synapse like this. In this test case, it is a private, non-federated server, so it would be logical that it keeps the room alive if it is public. Deleting the room (and all of its history) should require an additional step. |
@huguesdk totally agreed. it's embarrassing that it's taken us this long to fix; thank you for the datapoint. matrix-org/matrix-spec-proposals#1777 is the proposed solution here. |
Deleting the empty room seems to have allowed me to reuse its alias. It can be tricky to identify the correct room though since the rooms list no longer shows the alias. |
This only works if you are the admin of the server. I lost access to a public room I created in matrix.org. I was the admin and now I cannot join and I cannot recreate it, so I guess that the room alias, the one that I published to some contacts it is lost and unusable. This is truly quite bad because:
|
Not quite, you should still be able to remove that alias from pointing at your old room, there'd just be no UI in Element Web to do such (unless you count finding it in the room directory and shift clicking it, the easter egg method, as UI) |
Thank you for your reply. The room does not appear anymore in the public list. It does not appear anywhere. But if I try to create a room with the same ID, it won't let me, saying that the room already exists. I only see the "delete room" method in the Admin API. So you say that I can do it using the API as a regular user? (quite user friendly, on the other hand) |
Submitted by @matthew:matrix.org
we need to keep a HS or two in the room somehow to 'keep the lights on' and preserve history even if all the participating users leave. this would also be helpful as a way for ASes to interact with rooms without needing an explicit AS user joined.
(Imported from https://matrix.org/jira/browse/SPEC-211)
Attachments:
https://matrix.org/jira/secure/attachment/10210/public-rooms.png
The text was updated successfully, but these errors were encountered: