Email or username:

Password:

Forgot your password?
Evv1L (Эвил)

@element (and SchildiChat) clients are hardcoded to use matrix.to invitation links, even if room is located on non-matrix.org instance (like pmOS room).

Russian providers blocked matrix.to and all your room links in your "decentralized" messenger are currently dead.

This is NOT how decentralized messengers work.

#Matrix

10 comments
Lyyn ☮️🦄 #2024-02-16

@Evv1L matrix.to has nothing to do with matrix.org.
Migration to matrix:// is in progress and was always considered the end goal. Unfortunately it has some drawbacks.

Evv1L (Эвил)

@lyyn
> matrix.to has nothing to do with matrix.org.
What do you mean? Who owns matrix.to then and why it's hardcoded in Element?

Lyyn ☮️🦄 #2024-02-16

@Evv1L
> clients are hardcoded to use matrix.to invitation links, even if room is located on non-matrix.org instance

It does not matter where the room is located. There has never been any logic which uses different links for different servers.

Lyyn ☮️🦄 #2024-02-16

@Evv1L It's hardcoded in almost all clients because it was the de-facto standard while matrix:// links are standardized

Sulian

@Evv1L you can put those links into your client to join still, the page on matrix.to just makes it prettier. matrix.to is also a very simple website, so anyone can host it and you just need to change the url, you can even change /etc/hosts to point to a non-blocked site.

Lyyn ☮️🦄 #2024-02-16

@sulian @Evv1L I think changing /etc/hosts won't help because TLS certificates on a different server won't match.

Sulian

@lyyn @Evv1L the idea was to just put 127.0.0.1 matrix.to, and then just `http-server . -ssl` in the matrix.to source directory, it will warn that the cert is self-signed, but that's fine

Sulian

@drq @lyyn @Evv1L it's just an example, the main point is that blocking matrix.to is just a minor inconvenience. Also you could probably make an extension that did something similar too

Go Up