Skip to content

Commit 90da216

Browse files
authored
Fix spec link in 2026-05-29-twim.md (#3444)
Signed-off-by: Kim Brose <2803622+HarHarLinks@users.noreply.github.com>
1 parent 858faf0 commit 90da216

1 file changed

Lines changed: 7 additions & 8 deletions

File tree

‎content/blog/2026/05/2026-05-29-twim.md‎

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ path = "/blog/2026/05/29/this-week-in-matrix-2026-05-29"
55

66
[taxonomies]
77
author = ["Thib"]
8-
category = ["This Week in Matrix"]
9-
10-
[extra]
8+
category = ["This Week in Matrix"]
9+
10+
[extra]
1111
image = "https://matrix.org/blog/img/2026-05-29-og.png"
1212
+++
1313

@@ -137,7 +137,7 @@ The Governing Board is an advisory board to The Matrix.org Foundation and with e
137137
138138
[HarHarLinks](https://matrix.to/#/@kim:sosnowkadub.de) announces
139139

140-
> It has long annoyed me that [matrix.to](https://matrix.to) URLs are in the unfortunate situation of being [specified](https://spec.matrix.org/latest/appendices/#matrix-uri-scheme) following [RFC 3986](https://tools.ietf.org/html/rfc3986), while Matrix room aliases use `#` as their "sigil". The nice part is that the fallback in many browsers and probably URL parsers allows someone to type in the literal ID after `https://matrix.to/#/` in a human readable/type-able way: `https://matrix.to/#/#matrix:matrix.org` and it will work. However that does not actually comply with the RFC spec for URLs, which mandates URL-encoding ("percent-encoding") for some special characters, including the `#`. The practical impact of this is that in some situations, URL parsers my stumble and misinterpret matrix.to URLs. We commonly see this at the Website & Content WG when writing YouTube descriptions: the second "illegal" `#` will be interpreted as a hashtag instead, breaking the link. I find this particularly annoying as some implementations, including Element and <https://matrix.to> itself actually prefer to generate "illegal" links. This has been a topic of discussion before, but so far has not been accepted.
140+
> It has long annoyed me that [matrix.to](https://matrix.to) URLs are in the unfortunate situation of being [specified](https://spec.matrix.org/latest/appendices/#matrixto-navigation) following [RFC 3986](https://tools.ietf.org/html/rfc3986), while Matrix room aliases use `#` as their "sigil". The nice part is that the fallback in many browsers and probably URL parsers allows someone to type in the literal ID after `https://matrix.to/#/` in a human readable/type-able way: `https://matrix.to/#/#matrix:matrix.org` and it will work. However that does not actually comply with the RFC spec for URLs, which mandates URL-encoding ("percent-encoding") for some special characters, including the `#`. The practical impact of this is that in some situations, URL parsers my stumble and misinterpret matrix.to URLs. We commonly see this at the Website & Content WG when writing YouTube descriptions: the second "illegal" `#` will be interpreted as a hashtag instead, breaking the link. I find this particularly annoying as some implementations, including Element and <https://matrix.to> itself actually prefer to generate "illegal" links. This has been a topic of discussion before, but so far has not been accepted.
141141
>
142142
> Meanwhile, we also have the [`matrix:` URI scheme](https://spec.matrix.org/latest/appendices/#matrix-uri-scheme) registered with IANA. Instead of the sigils, it uses letters like `r/` for aliases: `matrix:r/matrix:matrix.org`. So at Matrix Community Summit last weekend, we had the idea to deprecate using sigils in matrix.to fragments altogether and replace them with `matrix:` URI style word characters. You can find all this packaged as [MSC4481](https://github.com/matrix-org/matrix-spec-proposals/pull/4481) including an implementation for <https://matrix.to>. Please feel free to test or implement in your own client. Thanks to all involved in the discussion and helping the implementation!
143143
@@ -159,9 +159,9 @@ Multiplatform Kotlin SDK for developing Clients, Bots, Appservices and Servers.
159159

160160
> You know how some other applications directly prompt you to open your native/web client, when you click on a link? Matrix has matrix.to, but it always prompts you to click on a button to open your client, even though we have a standardized scheme to do that (matrix: URIs)!
161161
>
162-
> I tried my hand at directly opening your matrix client from the matrix.to page. You can try it out and review it here: <https://github.com/matrix-org/matrix.to/pull/409>
163-
164-
### WukkieMail
162+
> I tried my hand at directly opening your matrix client from the matrix.to page. You can try it out and review it here: <https://github.com/matrix-org/matrix.to/pull/409>
163+
164+
### WukkieMail
165165

166166
[Joop Kiefte 🟙 (LaPingvino)](https://matrix.to/#/@joop:chat.kiefte.eu) says
167167

@@ -267,7 +267,6 @@ Join [#ping:maunium.net](https://matrix.to/#/#ping:maunium.net) to experience th
267267
|9|waywardinn.com|372|
268268
|10|nhjkl.com|374.5|
269269

270-
271270
## That's all I know
272271

273272
See you next week, and be sure to stop by [#twim:matrix.org](https://matrix.to/#/#twim:matrix.org) with your updates!

0 commit comments

Comments
 (0)