98 lines
3.4 KiB
Plaintext
98 lines
3.4 KiB
Plaintext
---
|
|
summary: Ability to remove room aliases from directory
|
|
---
|
|
assignee: erikj
|
|
created: 2014-09-15 23:26:15.0
|
|
creator: matthew
|
|
description: |-
|
|
Rooms currently can never ben destroyed from the room list. So if someone accidentally creates ##sillyname:matrix.org:matrix.org or something similarly embarassing, there's no way to edit the directory to remove the alias.
|
|
|
|
We should support this asap to let people clean up their mistakes.
|
|
id: '10002'
|
|
key: SYN-2
|
|
number: '2'
|
|
priority: '1'
|
|
project: '10000'
|
|
reporter: matthew
|
|
resolution: '1'
|
|
resolutiondate: 2014-09-30 11:32:05.0
|
|
status: '5'
|
|
type: '2'
|
|
updated: 2014-11-20 10:06:36.0
|
|
votes: '0'
|
|
watches: '3'
|
|
workflowId: '10336'
|
|
---
|
|
actions:
|
|
- author: kegan
|
|
body: Should there be permissions locking down who can do this? If I create an alias, does that mean only I can delete it? What's stopping people from modifying existing aliases to point to !nasty_room_id:matrix.org ?
|
|
created: 2014-09-22 09:07:54.0
|
|
id: '10359'
|
|
issue: '10002'
|
|
type: comment
|
|
updateauthor: kegan
|
|
updated: 2014-09-22 09:07:54.0
|
|
- author: matthew
|
|
body: Yes, it needs a permission. Surely the matrixy way to do this is to define a threshold powerlevel for a room beyond which you're allowed to diddle its alias.
|
|
created: 2014-09-22 23:30:23.0
|
|
id: '10371'
|
|
issue: '10002'
|
|
type: comment
|
|
updateauthor: matthew
|
|
updated: 2014-09-22 23:30:23.0
|
|
- author: kegan
|
|
body: Aliases are completely separate from the room itself. I can create aliases for a room I'm not even in.
|
|
created: 2014-09-23 10:15:20.0
|
|
id: '10381'
|
|
issue: '10002'
|
|
type: comment
|
|
updateauthor: kegan
|
|
updated: 2014-09-23 10:15:20.0
|
|
- author: matthew
|
|
body: Well, we surely don't want to have a totally separate ACL system for aliases. Can't we mandate that HSes only let you create aliases for rooms which you are in, and the powerlevel of the person who created an aliases is stored and replicated over that room, and can only be edited by people with higher powerlevel?
|
|
created: 2014-09-23 12:24:36.0
|
|
id: '10392'
|
|
issue: '10002'
|
|
type: comment
|
|
updateauthor: matthew
|
|
updated: 2014-09-23 12:24:36.0
|
|
- author: kegan
|
|
body: |-
|
|
The problem is that they are two completely different systems. Room state != Directory server data. As I said on IRC:
|
|
{quote}
|
|
<kegan> #room:nastydomain.com is free to point at whatever the hell it likes, nastydomain.com doesn't need to be running a HS, and the room ID it points to will have no idea I've pointed to it.
|
|
{quote}
|
|
created: 2014-09-23 13:43:38.0
|
|
id: '10396'
|
|
issue: '10002'
|
|
type: comment
|
|
updateauthor: kegan
|
|
updated: 2014-09-23 13:43:38.0
|
|
- author: matthew
|
|
body: Have split out the wider permissions discussion into SYN-66. SYN-2 remains as the functional bug.
|
|
created: 2014-09-23 14:16:33.0
|
|
id: '10398'
|
|
issue: '10002'
|
|
type: comment
|
|
updateauthor: matthew
|
|
updated: 2014-09-23 14:16:33.0
|
|
- author: matthew
|
|
body: |-
|
|
A first cut on this would be to just have the server admin responsible for doing so - although in practice they can do that already by just editing the table in sqlite on the HS in question.
|
|
|
|
Having it self-service would be much nicer...
|
|
created: 2014-09-23 15:43:14.0
|
|
id: '10409'
|
|
issue: '10002'
|
|
type: comment
|
|
updateauthor: matthew
|
|
updated: 2014-09-23 15:43:14.0
|
|
- author: erikj
|
|
body: Server admins can now delete room aliases.
|
|
created: 2014-09-30 11:32:28.0
|
|
id: '10482'
|
|
issue: '10002'
|
|
type: comment
|
|
updateauthor: erikj
|
|
updated: 2014-09-30 11:32:28.0
|