| 6 Mar 2025 |
 emily | your homeserver couldn't even take over the room if it wanted to | 18:39:56 |
| emily | state resolution is completely distributed | 18:40:00 |
| 7 Mar 2025 |
|  Qyriad changed their display name from Qyriad to qyriad. | 16:42:15 |
| 8 Mar 2025 |
 @emma:rory.gay | if you want federation traffic to cease you still need to leave all rooms for all users | 01:46:32 |
 f0x | In reply to @emilazy:matrix.org
room IDs are opaque identifiers that happen to encode one homeserver for no real good reason well, so the server that created it can guarantee global uniqueness | 03:34:15 |
| emily | because if you were just relying on 128 bits of good old-fashioned entropy you could have two starved VMs that accidentally create the same room? | 03:35:26 |
| emily | seems like you'd run into cryptography problems in such a setting anyway | 03:36:10 |
| f0x | In reply to @emilazy:matrix.org
because if you were just relying on 128 bits of good old-fashioned entropy you could have two starved VMs that accidentally create the same room? rather stuff like a malicious entity claiming they created a (different) room with that id, I think | 03:38:06 |
| emily | I guess I don't understand the protocol well enough to grok the threat model. (I don't really know how room creation works at all) | 03:38:49 |
| emily | my understanding was that there was work on getting the homeserver out of room IDs, though? | 03:39:01 |
| emily | (and out of user IDs but I think that stalled) | 03:39:06 |
