Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Welcoming Rocket.Chat to Matrix

matrix.org

Post reply on HN
Print view View original

21–30 of 81 posts

Re: Welcoming Rocket.Chat to Matrix

#21

Post by ducktective »

Macha wrote: post #14
ducktective wrote: post #12

Can someone explain in layman terms what Rocket.Chat is? Is it a Matrix client like Element? Is it a protocol?

Rocket.Chat is basically selfhosted slack. 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.…

Thanks! So they have their own protocol and client. But, they have made a bridge with matrix.

They could have just created a matrix client instead of the whole business model...

Re: Welcoming Rocket.Chat to Matrix

#22

Post by woojoo666 »

Macha wrote: post #14
ducktective wrote: post #12

Can someone explain in layman terms what Rocket.Chat is? Is it a Matrix client like Element? Is it a protocol?

Rocket.Chat is basically selfhosted slack. 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.…

At the end of the article they posted an update:

> Aaron from Rocket.Chat just published an excellent guide & video tour for how to actually set up your Rocket.Chat instance with Dendrite

Dendrite is a Matrix homeserver[1] so it looks like you can mix and match

[1]: https://matrix.org/docs/projects/try-matrix-now#servers

Re: Welcoming Rocket.Chat to Matrix

#23

Post by SargeZT »

ducktective wrote: post #21
Macha wrote: post #14

Earlier quoted context omitted.

Rocket.Chat is basically selfhosted slack. 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.…

Thanks! So they have their own protocol and client. But, they have made a bridge with matrix. They could have just created a matrix client instead of the whole business model...

Matrix was still a part of Amdocs and basically not a thing beyond a protocol and a WebRTC demo When RocketChat was created.

Re: Welcoming Rocket.Chat to Matrix

#24

Post by zufallsheld »

ducktective wrote: post #21
Macha wrote: post #14

Earlier quoted context omitted.

Rocket.Chat is basically selfhosted slack. 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.…

Thanks! So they have their own protocol and client. But, they have made a bridge with matrix. They could have just created a matrix client instead of the whole business model...

Well, matrix is from 2014, rocketchat from 2015. I don't know if matrix was this popular and mature in 2014 to adopt it to build a business around it.

Re: Welcoming Rocket.Chat to Matrix

#25

Post by woojoo666 »

0des wrote: post #18
woojoo666 wrote: post #13

Earlier quoted context omitted.

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/

The question was due to the tight relationship between the two, not due to a misunderstanding. Im a daily user of Matrix, many clients.

I see, my mistake. The coupling is definitely tight. I think the developers across Matrix and Element are largely the same too right? Ideally I would hope that the Matrix team can focus on the protocol, but I can see why they needed to build Element as a way to sell the protocol to the masses. But perhaps now that we have fully-featured front-ends like Rocket chat joining in, the Matrix team can dedicate more of them time to the protocol

Re: Welcoming Rocket.Chat to Matrix

#26

Post by walrus01 »

Macha wrote: post #14
ducktective wrote: post #12

Can someone explain in layman terms what Rocket.Chat is? Is it a Matrix client like Element? Is it a protocol?

Rocket.Chat is basically selfhosted slack. 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.…

> 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 not federate.

https://github.com/matrix-org/synapse

I have one setup where the synapse daemon lives on a VM that's only accessible in company internal RFC1918 IP space so you can only connect to it if your laptop or other device is also on a split tunnel VPN.

Of course you could run it with a public IP as well.

Re: Welcoming Rocket.Chat to Matrix

#27

Post by Arathorn »

tabbott wrote: post #17
ramboldio wrote: post #2

This is what a aquisition in Open Source land looks like.. :D

I don't think this is an acquisition -- Rocket.Chat remains an independent, venture-backed company. Unless I'm missing something hidden here, this announcement is just Rocket.Chat implementing an integration with Matrix, not a change in control of their open source project or associated business.

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!

Re: Welcoming Rocket.Chat to Matrix

#28

Post by Rechtsstaat »

tabbott wrote: post #17
ramboldio wrote: post #2

This is what a aquisition in Open Source land looks like.. :D

I don't think this is an acquisition -- Rocket.Chat remains an independent, venture-backed company. Unless I'm missing something hidden here, this announcement is just Rocket.Chat implementing an integration with Matrix, not a change in control of their open source project or associated business.

I think that is what they mean—the 'acquisition' in Open Source land is just the successful integration of one open platform into the other!

Re: Welcoming Rocket.Chat to Matrix

#30

Post by tabbott »

Arathorn wrote: post #27
tabbott wrote: post #17

Earlier quoted context omitted.

I don't think this is an acquisition -- Rocket.Chat remains an independent, venture-backed company. Unless I'm missing something hidden here, this announcement is just Rocket.Chat implementing an integration with Matrix, not a change in control of their open source project or associated business.

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 :)
Post reply on HN