You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, it is not quite clear that those IDs and alias are example, and it should be considered what kind of strings indicate room IDs and aliases better, such as:
!example:example.com
!exampleRoom:example.com
!example1:example.com, !example2:example.com
!room1:example.com, !room2:example.com
!alicesRoom:example.com, !bobsRoom:example.com
…
To Reproduce
Expected behavior: Choose a better example room ID and alias ahead of Matrix Protocol itself, and track them on a style guide
I like the idea of addressing it in the spec itself. The pushback would likely be that room IDs are going to be randomized strings rather than a word. This could create confusion when people can't set the room IDs themself. I do think at least having a consistent random example may be better.
Describe the bug
#3653 replaced room IDs and alias with ones on the Matrix Specification.
See:
!qporfwt:matrix.org
is used as an example.!aaabaa:matrix.org
is used as an example.#matrix:example.org
is used as an example.However, it is not quite clear that those IDs and alias are example, and it should be considered what kind of strings indicate room IDs and aliases better, such as:
!example:example.com
!exampleRoom:example.com
!example1:example.com
,!example2:example.com
!room1:example.com
,!room2:example.com
!alicesRoom:example.com
,!bobsRoom:example.com
To Reproduce
Expected behavior: Choose a better example room ID and alias ahead of Matrix Protocol itself, and track them on a style guide
Matrix Server:
Ansible:
Client:
Additional context
Taking them as an issue on https://github.com/matrix-org/matrix-spec-proposals would be an idea, though I am not sure whether the proposal could be picked up as friendly or hostile.
The text was updated successfully, but these errors were encountered: