| 8 Mar 2025 |
 f0x | In reply to @emilazy:matrix.org
my understanding was that there was work on getting the homeserver out of room IDs, though? I'm not sure? They were removed from event id's because they were no longer needed there | 03:42:43 |
 @emma:rory.gay | no, the room id is a hash of the create event iirc | 04:25:49 |
| @emma:rory.gay | its just to avoid conflicts between homeservers | 04:26:01 |
 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 |
| emily | but if the home server isn't authenticated you can put whatever you want there, right? | 13:21:06 |
| Cat | Its authenticated as part of the auth rules. | 13:28:59 |
| Cat | The homeserver of the room ID is authenticated via the homeserver of the user who sent the creation event and all that ties back to homeserver signing keys and TLS. | 13:29:40 |
| Cat | * The homeserver of the room ID is authenticated via the homeserver of the user who sent the creation event and all that ties back to homeserver signing keys and TLS. (TLS isnt involved in homeserver signing keys but is involved in being able to even start the process of claiming you are a certain homeserver) | 13:30:10 |
|  pacha left the room. | 13:48:33 |
| emily | getting mixed messages here :) but ok, that makes some more sense | 14:11:18 |
| @emma:rory.gay | yeah i was wrong lol | 14:50:31 |
|  Qyriad changed their display name from qyriad to Qyriad. | 21:41:03 |
| 9 Mar 2025 |
|  @hurdpublic:pub.solar joined the room. | 11:41:03 |
| @hurdpublic:pub.solar changed their profile picture. | 14:07:47 |
| @hurdpublic:pub.solar changed their profile picture. | 14:29:23 |
 WeetHet | I wonder if it's just me having issues with the #flakes:nixos.org's room name | 15:59:47 |
| WeetHet | 
Download Screenshot 2025-03-09 at 18.00.02.png | 16:00:19 |
| WeetHet | This is what I see | 16:00:21 |
| emily | probably split-brain | 16:02:15 |
| WeetHet | It's reported correctly in Element X on my phone | 16:05:46 |
 syd installs gentoo (they/them) | In reply to @weethet:catgirl.cloud
sent an image. Yeah it's a broken mess. Matrix is a dysfunctional protocol. | 16:19:58 |
| WeetHet | Who should we ask to create a room under NixOS/Community? | 19:15:23 |
|  Niklas Korz joined the room. | 19:16:04 |
