| 16 Jan 2025 |
 K900 | And I don't have access to @admin:nixos.org | 17:10:20 |
 Dandellion | There is an id, you can link https://matrix.to/#/!CTCrFzsBPYmDLmrja4:0upti.me?via=nixos.org&via=matrix.org&via=raccoon.college | 17:10:52 |
| Dandellion | https://matrix.to/#/!CTCrFzsBPYmDLmrja4:0upti.me?via=nixos.org&via=matrix.org&via=raccoon.college | 17:10:58 |
 emily | congrats on getting your domain immortalized | 17:11:15 |
 @emma:rory.gay | In reply to @emilazy:matrix.org
congrats on getting your domain immortalized Who? | 17:12:16 |
| emily | k900 | 17:12:32 |
| @emma:rory.gay | In reply to @k900:0upti.me
There is no ID yet Was the room not upgraded yet? :blobfox_confused: | 17:12:40 |
| @emma:rory.gay | In reply to @emilazy:matrix.org
k900 Oh lol | 17:12:48 |
| Dandellion | it's just 0upti.me part of the (completely arbitrary) roomid string | 17:13:06 |
| emily | does anyone know how to get the link to the old room in a way that doesn't involve scrolling through all history ever | 17:14:15 |
| emily | I don't seem to be able to rejoin !kjdutkOsheZdjqYmqp:nixos.org or add it to a space or anything | 17:14:24 |
| emily | I am worried it is going to be miserable the next time I want to look up some past discussion | 17:14:34 |
| Dandellion | It ca search across room upgrade boundaries | 17:19:49 |
| Dandellion | * | 17:21:00 |
| Dandellion | Generally clients are "smart" and make upgraded rooms shadow the older room. You're still joined to the old room - it just doesnt show up in your room list | 17:22:25 |
| emily | hmm, okay. | 17:25:18 |
| emily | then I wonder why they don't just integrate the history into the scrollback | 17:25:18 |
| @emma:rory.gay | In reply to @dandellion:dodsorf.as
It can search across room upgrade boundaries "it" depends on client implementation | 17:25:23 |
| @emma:rory.gay | Element isnt the standard for matrix | 17:25:45 |
| emily | it kinda very clearly is | 17:28:40 |
| emily | given that it seems like the spec is driven by what Element wants and other clients only ever come up as lip service to the idea of being a diverse ecosystem and are otherwise totally neglected | 17:29:34 |
| emily | and the fact that Element is the only client that doesn't run into interop issues and "we don't use that feature here (but we can't turn it off)" type stuff as a result | 17:30:09 |
| emily | I don't think that's good, but I do think it's the reality | 17:30:20 |
| @emma:rory.gay | In reply to @emilazy:matrix.org
given that it seems like the spec is driven by what Element wants and other clients only ever come up as lip service to the idea of being a diverse ecosystem and are otherwise totally neglected Its a topic that came up in the ecosystem governing board meeting this week, actually | 17:35:39 |
| emily | I am sceptical that that is a board with the power to stop Element implementing whatever they want and making it into a de facto standard. | 17:36:20 |
 Cat | The spec for room upgrades makes this behavior pretty standard. | 17:36:21 |
| Dandellion | In reply to @emilazy:matrix.org
given that it seems like the spec is driven by what Element wants and other clients only ever come up as lip service to the idea of being a diverse ecosystem and are otherwise totally neglected Im (still) giving them the benefit of the doubt here. This seems less true recently, user facing features just aren't being specced. While the spec team is actually doing more fundamental work.
Focusing on core matrix issues is a valid strategy that isnt neccecarily element specific
| 17:36:39 |
| @emma:rory.gay | In reply to @emilazy:matrix.org
I am sceptical that that is a board with the power to stop Element implementing whatever they want and making it into a de facto standard. I guess the matrix.ort foundation cant stop element doing element things | 17:36:50 |
| emily | I did a lot of giving the ecosystem the benefit of the doubt from 2018 onwards | 17:37:22 |
| emily | unfortunately the benefit has expired :P | 17:37:27 |
