Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Sure, Matrix is a thing, but every time I look at it, all I see is criticism of its specifications and poor interoperability between implementations?

Not sure what you're talking about. Everything is working fine for me, and they even conduct a whole conference about it annually: https://2024.matrix.org/

With a large number of clients and servers and the lack of a walled garden (like with Signal), you will always find something non-interoperable. It doesn't mean that you have to use it.






I'm not talking about the client ecosystem. I'm talking about the server ecosystem. There is only one fully-featured one, Synapse, everything else is in Alpha or Beta, feature-incomplete, or abandoned.

When I looked into writing my own implementation, the protocol seemed underspecified to me. "Do what synapse does" seemed to be the concensus.

This was a few years ago, so maybe things have improved. But given that no new feature complete servers have appeared, I doubt it.


All I said applies to servers, and I even mentioned servers explicitly. Why don't you want to use Synapse?

> "Do what synapse does" seemed to be the concensus.

What's wrong with that?


Is it really an open ecosystem if there's only one real implementation? Is there really a specification if the reference implementation is the real specification? Do we want to put all of our eggs into one basket? YMMV, but for me the answer to all those questions is "no".

Perfect is the enemy of the good.

Matrix is crap. If you want a serious alternative use XMPP with OMEMO or just use Email.

Care to elaborate on why you think it's crap, instead of just shitting on it? The latter is not terribly helpful to the discussion.



Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: