11–20 of 81 posts
A new implementation of the same thing, now on a different platform. Is it just me or does it seem like there are certain places where there is little innovation?
I'd argue basic chat functionality is a solved problem, and if Rocket.Chat deprecates their need to build and support that, they can focus entirely on value add/innovation.
Earlier quoted context omitted.
I'd argue basic chat functionality is a solved problem, and if Rocket.Chat deprecates their need to build and support that, they can focus entirely on value add/innovation.
I wonder how this will effect Riot, now Element
Can someone explain in layman terms what Rocket.Chat is? Is it a Matrix client like Element? Is it a protocol?
They now have a feature where it can federate with matrix. This means rocketchat users on your rocketchat instance can talk to matrix users on a federated matrix network if you enable it.
This means you could use the Rocket.chat server and Rocket.chat UI as an alternative to a homeserver + matrix client.
I don't believe this allows using a matrix client to connect to rocket.chat server's directly or vice versa.
Can someone explain in layman terms what Rocket.Chat is? Is it a Matrix client like Element? Is it a protocol?
Earlier quoted context omitted.
I'd argue basic chat functionality is a solved problem, and if Rocket.Chat deprecates their need to build and support that, they can focus entirely on value add/innovation.
I wonder how this will effect Riot, now Element
Element targets individuals participating largely in public chat rooms, I suspect it's design will remain significantly different for that reason.
Different apps with different purposes, but compatible.
This is what a aquisition in Open Source land looks like.. :D
Earlier quoted context omitted.
I wonder how this will effect Riot, now Element
There are multiple chat clients that support Matrix already [1], Element is just one of them. Separation of concerns is a good thing as products mature [1]: https://matrix.org/clients/
Earlier quoted context omitted.
I wonder how this will effect Riot, now Element
I suspect the market is different enough to matter. Rocket.Chat caters heavily to the Slack/Teams-type business chat. Federation to it likely often means federating with partner businesses also using Rocket.Chat. Element targets individuals participating largely in public chat rooms, I suspect it's design will remain significantly different for that reason. Different apps with different purposes, but compatible.
Earlier quoted context omitted.
Gee, I wonder who acquired Fediverse then - everyone's speaking ActivityPub. /s
As someone curious about this comment, can you articulate it in a way that would work in spoken words? the /s throws it off, like when people speak verbal hashtags, and my brain flies into the wall at velocity trying to break it down.
The thread's topic is likely similar, Matrix being another protocol used by many things.