I thought Gitter had already been acquired by GitLab?
That is correct - in 2017 https://about.gitlab.com/blog/2017/03/15/gitter-acquisition/. But as announced today, Gitter will be going to Matrix going forward.
51–60 of 124 posts
I thought Gitter had already been acquired by GitLab?
That is correct - in 2017 https://about.gitlab.com/blog/2017/03/15/gitter-acquisition/. But as announced today, Gitter will be going to Matrix going forward.
Earlier quoted context omitted.
Hopefully they'll be happy that Gitter will sprout all Matrix's funky features like E2EE, VoIP, Widgets, Read receipts, Reactions, a bajillion clients/bots/bridges, the open standard API itself... and as long as Element-branded-as-Gitter looks and performs and smells enough like Gitter, and the community & rooms are still there, all will be well. And if they don't like it, they can always go spin up their own Gitter…
This is the "slippers and sex toy" deflection. If the user's don't like the slippers (new features) they can use the sex toy to fornicate themselves.
> Our plan is instead to merge Gitter’s features into Element (or next generations of Element) itself and then - if and only if Element has achieved parity with Gitter based on the above list - we expect to upgrade the deployment on gitter.im to a Gitter-customised version of Element. The inevitable side-effect is that we’ll be adding new features to Element rather than Gitter going forwards. Wonder what existing Git…
Using it mostly out of necessity (a project I'm involved in uses it for communication), but I'm mostly enthusiastic about no longer having that annoying Matrixbot - there were always a number of Matrix users, and the implementation was incredibly confusing. It's a nice bonus that I'll no longer be dependent on Gitter's somewhat buggy Web UI. (That said, I am somewhat sceptical about whether we'll see any reasonable r…
As Element we are if nothing else highly financially motivated to get Gitter bridged into Matrix, so we can run it via our normal Matrix server backend farm rather than keep an entirely parallel deployment running of Gitter infrastructure. We also want to stick to our word :)
This is awesome. I found Gitter super handy because of it's close tie to repos, but being able to reach it from Element would be really nice.
You already could, before this announcement. For example, want to join https://gitter.im/hashicorp-consul/Lobby ? Then join #gitter_hashicorp-consul=2FLobby:matrix.org from Element.
I really like to use IRC on the terminal via Irssi. Can Irssi be used to access this matrix thing? If not, is there some nice matrix command line client in the Debian repos? Or maybe someone could just make an IRC server which is a bridge to matrix?
Just a few days ago I considered setting up a Gitter-bridge for my Marrix-instance, but decided that it was both too involved and not well-enough integrated to be worth it.
This is really good news!
Interesting. Is there already a Gitter->Matrix bridge, and that would essentially be going away once Gitter fully supports Matrix? It seems like they're not changing Gitter to talk Matrix, but actually switching the backend to be Matrix? Is that right?
The long term plan folding gitter.im features into Element and Gitter users will migrate to using Element and Matrix.
I really like to use IRC on the terminal via Irssi. Can Irssi be used to access this matrix thing? If not, is there some nice matrix command line client in the Debian repos? Or maybe someone could just make an IRC server which is a bridge to matrix?
Earlier quoted context omitted.
I'm really excited about this too, but I'm afraid it does matter. Gitter of it's own accord federating with matrix would be a watershed moment of a competitor laying down it's arms for the greater good, a détente in capitalism, and a really good sign for the future of all things Federated. Element acquiring Gitter is normal M&A, normal business. It's still good for Matrix and good for Gitter users, and we're still ch…
I love this move, since I'm trying to move to Matrix as my primary chat where possible. Even more so since some of the mentioned features are sorely needed in Element, like threads. But Gitlab is a for-profit company. I don't see this as Gitter laying down arms, but rather as Gitlab not being able to monetize Gitter enough to justify keeping it in the company. They probably sold it for a very reasonable amount.
That is indeed not what happened. It's just an acquisition. It does not actually give us hope that there's more momentum towards competitors being willing to play together in federation, that's not what happened.
Not sure why the one who made that point is getting downvoted, I think it's an interesting observation. That the press release arguably kind of intentionally tries to hand wave over a bit.
GitLab hasn't been giving it any attention. All they need is a checkmark in their portfolio.