Earlier quoted context omitted.
Yup, this is not an acquisition of any kind; Rocket.Chat just went and independently added native Matrix interoperability into their core product. It's basically celebrating this PR: https://github.com/RocketChat/Rocket.Chat/pull/23688 :) tabbott: we should so do this with Zulip - I think Matrix almost has all the threading primitives needed to bridge successfully now!
Yeah let's chat about it! We've overdue for catching up in any case :)
Welcoming Rocket.Chat to Matrix
61–70 of 81 posts
Re: Welcoming Rocket.Chat to Matrix
#62Rocket.Chat uses their own E2EE scheme [1] which is different and arguably less secure than the one in Matrix [2]. As I understand it, this is simply a bridge and will defeat the purpose of the advanced E2EE algorithm in Matrix. I recall looking at Rocket.Chat when setting up chat servers for my corporation and dropping it over their poor and slow to adopt E2EE implementations. [1] https://docs.rocket.chat/guides/sec…
Even if Rocket.Chat used the same E2EE scheme as Matrix, you would still have to re-encrypt, given the application-layer protocols are not the same. RC's messages are a blob of JSON which looks nothing like Matrix's JSON events. To preserve E2EE throughout you'd have to speak precisely the same protocol - e.g. Matrix+Megolm or XMPP+OMEMO or whatever, or effectively run a multihead stack (one which can speak both Matr…
To be fair, though E2EE is perfect for a general purpose messenger, I don't think it's necessary per se. Group chats that would normally appear on IRC don't have a need for E2EE (and verifying everyone in a public room is also extremely impractical!) which seems like a perfect use case for this integration.
Re: Welcoming Rocket.Chat to Matrix
#63HN frequently seems obsessed with Matrix. So I want to ask, where do you all hang out and how do you use it? I think Matrix is cool, I just am not sure how people are actually using it. Please don't tell me to look at the channels list there's a lot of porn and most channels I have joined are dead.
Re: Welcoming Rocket.Chat to Matrix
#64Earlier quoted context omitted.
rocketchat already had federation, but it is/was awful
It definitely was still in its infancy. But I think this is where Rocket.Chat's decision makes tons of sense. Matrix has spent as many years I think as Rocket.Chat focusing on a protocol. So makes perfect sense to leverage all of that time and learnings. Not to mention it means Federation with anyone that chooses to implement this common protocol. So beyond business interest alone but contributing to the greater ecos…
* Matrix has spent as many years I think as Rocket.Chat —> * Matrix has been around about as long as Rocket.Chat but focused heavily on federation
Re: Welcoming Rocket.Chat to Matrix
#65Earlier quoted context omitted.
> Rocket.Chat is basically selfhosted slack. What would this accomplish that self hosting synapse doesn't? It's totally possible to self host the official matrix 'synapse' daemon for self hosted slack-like functionality within an organization, and use the official 'element' client or any other compliant matrix protocol client. If it's for something like company slack-like functionality you can choose to federate or n…
> It's totally possible to self host the official matrix 'synapse' daemon for self hosted slack-like functionality within an organization, and use the official 'element' client or any other compliant matrix protocol client. If it's for something like company slack-like functionality you can choose to federate or not federate. Having attempted to do exactly this recently, let me assure you that while it may be technic…
Re: Welcoming Rocket.Chat to Matrix
#66Earlier quoted context omitted.
Yeah let's chat about it! We've overdue for catching up in any case :)
Wasn't the work (not the result) "announced" already during FOSDEM 1.5 years ago? Real world moving more slowly? Just an observation, it happens to all of us...
Re: Welcoming Rocket.Chat to Matrix
#67Earlier quoted context omitted.
> It's totally possible to self host the official matrix 'synapse' daemon for self hosted slack-like functionality within an organization, and use the official 'element' client or any other compliant matrix protocol client. If it's for something like company slack-like functionality you can choose to federate or not federate. Having attempted to do exactly this recently, let me assure you that while it may be technic…
What? Almost every statement here is wrong. There are tonnes of unfederated Matrix servers out there, and E2EE and SSO is completely orthogonal to federation. History retention does apply to encrypted events. And Synapse only tends to use lots of resources when federated into large public rooms (these days). I’m terrified at what must have gone wrong such that you ended up drawing these conclusions :s
> There are tonnes of unfederated Matrix servers out there,
No way to know for sure, but it certainly isn't a well-supported configuration.
> History retention does apply to encrypted events.
> Note that message retention policies don't apply to state events.
https://github.com/matrix-org/synapse/blob/develop/docs/mess...
> And Synapse only tends to use lots of resources when federated into large public rooms (these days)
Synapse used 30-50% of 1 CPU and ~1GB memory at idle with 1 room and 0 connected clients.
Re: Welcoming Rocket.Chat to Matrix
#68HN frequently seems obsessed with Matrix. So I want to ask, where do you all hang out and how do you use it? I think Matrix is cool, I just am not sure how people are actually using it. Please don't tell me to look at the channels list there's a lot of porn and most channels I have joined are dead.
Matrix is where open source projects move their chat rooms when they don't actually want public input.
Re: Welcoming Rocket.Chat to Matrix
#69Earlier quoted context omitted.
Wasn't the work (not the result) "announced" already during FOSDEM 1.5 years ago? Real world moving more slowly? Just an observation, it happens to all of us...
hm, i don’t remember announcing anything on the Matrix side? i might have namedropped that we’d been discussing it as a possibility tho!
Re: Welcoming Rocket.Chat to Matrix
#70Desktop web clients worked always.
It's probably a websockets issue.
I tried running behind haproxy and traefik, same problem.
I tried following some advice I got from a maintainer in their forums, same problem.
I went back to Mattermost.
Is a shame, rocket chat UI seems nicer to me than mattermost