| 8 Mar 2025 |
 Ralith | In reply to @f0x:pixie.town
rather stuff like a malicious entity claiming they created a (different) room with that id, I think if anything, having the hs in the id makes that easier since it's predictable but not authenticated in any way | 08:28:23 |
| Ralith | it was always a kinda baffling decision | 08:28:34 |
 Cat | In reply to @emma:rory.gay
no, the room id is a hash of the create event iirc It’s not. That’s the proposed solution to make them not have a homeserver in there. | 10:38:02 |
| Cat | The room ID is an opaque string with 0 meaning and no defined algorithm for its creation just a rule about that the origin hs is the same as room creator. | 10:39:12 |
 emily | In reply to @ralith:ralith.com
if anything, having the hs in the id makes that easier since it's predictable but not authenticated in any way okay yeah this is what I was unsure about | 13:08:16 |
| emily | so it's truly pointless | 13:08:40 |
| emily | In reply to @cat:feline.support
The room ID is an opaque string with 0 meaning and no defined algorithm for its creation just a rule about that the origin hs is the same as room creator. I'm surprised people don't use it to put fake vanity domains in | 13:08:41 |
| Cat | The full ruleset for room ids are !*:homeserver and the * represents all legal characters. | 13:16:48 |
