Skip to main content

Why the hell is the stance of some @matrix and @element people that web browsers should implement 1) a client side matrix.to alternative or 2) redirect to matrix.to if no Matrix client is found AS A REQUIREMENT for clients to actually switch to using matrix: URIs. Wouldn't a first step be to actually REGISTER such a link handler with the OS instead of using some custom, undocumented element URI scheme. Supporting the link internally is just not enough for widespread adoption...

#matrix

#matrix @The Matrix.org Foundation @Element
in reply to famfo

The Matrix.org Foundation
The Matrix.org Foundation
• •
can you link to the issue where this is being said? Obviously having clients register matrix: URIs with the OS is desirable, otherwise what's the point.
in reply to The Matrix.org Foundation

famfo
famfo
• •

element-web issue: github.com/element-hq/element-…
matrix.to issue: github.com/matrix-org/matrix.t…

I'd like to move away from using matrix.to links, web browsers have already marked the matrix URI as "safe" but the client people call the entire chat protocol by doesn't actually register a link handler with the OS.


Support matrix URI scheme · Issue #16875 · element-hq/element-web

matrix-org/matrix-spec-proposals#2312 The MSC has been accepted and will be in an upcoming version of the spec.
GitHub
⇧