Neither exists: matrix.to appears only in the account panels, and there is no view-source anywhere.
Both are in Element's message menu and both are what somebody reaches for when reporting a problem - a permalink is how a message is quoted to somebody else, and the source is how a malformed event is described to whoever can fix it. This client has neither, so a bug in a room can only be described in prose.
Neither exists: `matrix.to` appears only in the account panels, and there is no view-source anywhere.
Both are in Element's message menu and both are what somebody reaches for when reporting a problem - a permalink is how a message is quoted to somebody else, and the source is how a malformed event is described to whoever can fix it. This client has neither, so a bug in a room can only be described in prose.
The link goes by canonical alias where the room has one, because an alias names a room to a person and carries its own server. Failing that it is the room id with via hints, and the hints are facts rather than guesses: the domain the room was made on, and this account's own server, which is known to be in the room because we are.
The source is fetched from the server rather than taken from the timeline — what is held here is what this client made of the event, and the whole point of looking is that what it made may be wrong. In an encrypted room both halves come back: the envelope every other client sees, and the plaintext it turned out to say. The panel leads with the plaintext and copies each half separately, since what gets pasted into a bug report is usually one of them.
Finished.
The link goes by canonical alias where the room has one, because an alias names a room to a person and carries its own server. Failing that it is the room id with `via` hints, and the hints are facts rather than guesses: the domain the room was made on, and this account's own server, which is known to be in the room because we are.
The source is fetched from the server rather than taken from the timeline — what is held here is what this client *made* of the event, and the whole point of looking is that what it made may be wrong. In an encrypted room both halves come back: the envelope every other client sees, and the plaintext it turned out to say. The panel leads with the plaintext and copies each half separately, since what gets pasted into a bug report is usually one of them.
[178b2a5](https://git.salastil.com/Salastil/moho/commit/178b2a5)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Neither exists:
matrix.toappears only in the account panels, and there is no view-source anywhere.Both are in Element's message menu and both are what somebody reaches for when reporting a problem - a permalink is how a message is quoted to somebody else, and the source is how a malformed event is described to whoever can fix it. This client has neither, so a bug in a room can only be described in prose.
Finished.
The link goes by canonical alias where the room has one, because an alias names a room to a person and carries its own server. Failing that it is the room id with
viahints, and the hints are facts rather than guesses: the domain the room was made on, and this account's own server, which is known to be in the room because we are.The source is fetched from the server rather than taken from the timeline — what is held here is what this client made of the event, and the whole point of looking is that what it made may be wrong. In an encrypted room both halves come back: the envelope every other client sees, and the plaintext it turned out to say. The panel leads with the plaintext and copies each half separately, since what gets pasted into a bug report is usually one of them.
178b2a5