Show Navigation
Conversation
Notices
-
Some of #Riot’s problems are baked into #Matrix as a whole. For example, addressing. Let’s say I set up #Synapse at matrix\.federati\.net. The “#members” room would be at #members:matrix.federati.net, correct? And my account would be @lnxw48a1:matrix.federati.net? I’m not even sure. Do their URLs start with “matrix:”? Or maybe “matrix://“?
And that’s the problem. They intentionally chose something so alien-looking that it confuses people.
-
@strypey My impression is that the other names are just aliases, and that the rooms themselves are not actually co-hosted. I could be wrong, but that's always been my impression.
-
@clacke True, the internal ID is "[some hash]:hostname". @strypey's impression is that the hostname part doesn't matter ... that if the original host goes down, the other homeservers that hold copies can keep the room alive and active. That is not the impression I've gotten, either as an active Matrix user or from various riot-*:matrix.org rooms that I'm in.
-
@strypey "are you on matrix.org or another homeserver?"
Both. It's interesting to observe room behavior when one or the other homeserver is down. It does not seem consistent with other aliases being more than just a pointer and local cache. But maybe I should rejoin matrix:matrix.org and ask the Matrix team to clarify this. (I'd read the Matrix spec, but the spec is outdated, with the current "spec" being "whatever Riot-Web and matrix.org do".)
@clacke
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
All Arkwood Pond Social content and data are available under the