2024-01-16 18:33:34 +01:00
2020-04-09 23:51:14 -07:00
2024-01-16 18:33:34 +01:00
2020-04-11 11:22:39 -07:00
2020-04-09 14:00:07 -07:00
2024-01-02 22:43:22 +01:00
2024-01-02 22:43:22 +01:00
2022-03-22 15:55:57 -07:00
2024-01-16 17:57:28 +01:00
2020-09-21 14:39:48 -07:00
2020-01-14 19:51:41 +01:00
2023-03-22 09:24:41 +01:00
2020-04-06 09:35:28 -07:00
2023-12-08 11:24:20 +01:00

Federation notes

There are 2 ports - client port and federation port. On Cloudron, the client port is reverse proxied, so we are good. The federation port is more complicated.

Matrix used to accept self-signed certs on the federation port before. This was based on some 'perspectives' approach. This was deemed a failure and they decided to go to having valid certs.

In MSC1711, which happenned a Matrix 1.0 time, it was decided to use valid certs. As part of this proposal, MSC1708 aka .well-known support was added.

The idea of .well-known is delegation. Site X can delegate to Matrix Site Y. Both require valid certs nevertheless.

The _matrix._tcp. SRV is:

$ host -t srv _matrix._tcp.example.org
_matrix._tcp.example.org has SRV record 0 0 8448 matrix.example.org.

The .well-known/matrix/server is:

{
   "m.server": "<server>[:<port>]"
}

Finally, to test federation go to federationtester - source.

Description
clone to test the MAS
Readme MIT 30 MiB
Languages
JavaScript 87.6%
HTML 11.7%
Shell 0.6%