-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 everyone leaves a room there's no way to then get into it to delete its alias so you can reuse the alias #3194
Comments
Somewhat related to #1361. you can delete it as a server admin, obvs. I guess we should extend that ability to people who had rights to remove the alias in the last known state of the room. |
vaguely relate to matrix-org/synapse#614 |
oops, i filed a duplicate at matrix-org/synapse/issues/2100 |
Can this not now be done by shift clicking or something wacky like that? I recall some weird easter egg about it mentioned |
@t3chguy I don't think so... |
@ara4n I seem to recall you saying something was shift clickable? |
i just found this: #1680 |
Shift-clicking as a server admin in the room directory should remove it. |
yeah, it only works as a server admin in the room directory, not room admins and not automatically after everyone leaves |
Hmm.. I managed to do this but the room is not in the room directory but I still have the internal ID.... using the internal ID though only gives me
|
the horrible hacky workaround is to delete the right row from room_aliases table in the DB. we need a proper solution (hence this bug) |
can one hit the |
Thanks you two! I used the |
What if the room goes dead, including the admin of the room, and someone else wants to use the room's alias? |
@quenz Yeah Sudoquai and me got the same problem. |
We need a solution for this - when can we expect a solution for this ? |
This should be handled on the server side by removing all aliases when the last local user leaves the room. It's not like the aliases would work without the server being in the room, so not much point in keeping them. |
Closing as a proposed workaround for what is fundamentally a server misbehaviour - see @tulir's message above |
I've reopened matrix-org/synapse#1307 with more info, so that we're tracking this (very valid) issue somewhere. It's all very well that the fix has been identified, but if it's not tracked on an open bug it's never going to happen. |
No description provided.
The text was updated successfully, but these errors were encountered: