5 ms·
The server-to-server specification was only formally released on February 5 of this year. Before that, it was certainly necessary to do reverse-engineering of s
by mindB 8y ago
The server-to-server specification was only formally released on February 5 of this year. Before that, it was certainly necessary to do reverse-engineering of synapse in order to build a HS, but it no longer is. The lack of server implementations just over a month after the release of the spec isn't good evidence of a bad spec. I strongly disagree with Jason's (who has been openly hostile to most of the matrix community including me) characterization of the spec in its current form.
Disclosure: I like matrix and have hacked on a few matrix-related projects as a hobby activity (Jason would refer to this as buying into Matthew's (the CEO of New Vector, the company primarily driving matrix) personal cult). That's it.
- maxidorius 8y agoAs the author of mxhsd [1] and Gridepo [2], I can sadly confirm Jason's claims that it is STILL necessary to reverse engineer to talk to the existing federation. Synapse doesn't follow the spec, which is a fact I'm experiencing every day. But more to that, there is no desire from its developers to ever comply with the spec, rather than changing the spec on a whim. And that are the reasons why making a HS is not possible: endless moving target. [1]: https://github.com/kamax-matrix/mxhsd https://github.com/kamax-matrix/mxhsd [2]: https://gitlab.com/kamax-io/grid/gridepo https://gitlab.com/kamax-io/grid/gridepo
- Arathorn 8y agoif anyone's curious about the unspecific complaints here, it transpires that the actual complaint is synapse had a bug where it some endpoints were called with a trailing slash when the spec said it shouldn't have one... it got fixed in https://github.com/matrix-org/synapse/pull/4840 https://github.com/matrix-org/synapse/pull/4840 and https://github.com/matrix-org/synapse/pull/4935 https://github.com/matrix-org/synapse/pull/4935.