5 ms·
Some of this article is poorly researched. Rocket.chat is not moving over to the protocol, it's just implementing federation in such a way that Rocket.Chat serv
by DoItToMe81 4y ago
Some of this article is poorly researched. Rocket.chat is not moving over to the protocol, it's just implementing federation in such a way that Rocket.Chat servers can communicate with Matrix servers. It's still its own (heavily flawed) thing.
- tcfhgj 4y agowhat's the difference?
- Arathorn 4y agoPersonally, I think it’s fine to say that X speaks Matrix if X speaks the Server-Server API, like Rocket.Chat or Gitter does. I think the distinction the grandparent post is making is that RC doesn’t speak the Client-Server API, so you can’t point a random Matrix client at it. Honestly, I think it matters more that you can talk to it transparently via the Matrix network than connect your favourite Matrix client to it.
- DoItToMe81 4y agoWell, you can't simply use Rocket.Chat to join a Matrix server. You need to join a Rocket.Chat server set up to communicate with Matrix and work from there. Neither can you use a Matrix client to join a Rocket.Chat instance.
- throwaway67743 4y agoBut at least their clients aren't awful, might actually be useful if it can talk matrix
- sanjayio 4y agoWhat makes you think it’s flawed?