61–70 of 124 posts
It is not obvious from the title but Element is actually acquiring Gitter. Quote from the article: > In practice, the way this is happening is that Element (the company founded by the Matrix core team to fund Matrix development) is acquiring Gitter from GitLab, with a combined Gitter and Element dev team focusing on giving Gitter a new life in Matrix! There is also another blogpost from the elements side https://elem…
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.
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…
> That said, I am somewhat sceptical about whether we'll see any reasonable results in a reasonable amount of time 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 :)
Additional topics discussed in our just-released conversation[1] with GitLab and Element leads: 1. What happened to "ChatOps" and why is GitLab divesting in this space? 2. Who contacted whom? What are some details of the acquisition process and negotiations? 3. What does this mean at a practical sense for existing Gitter users? 4. What's going to happen in the next 6, 12, and 18 months? [1]: https://changelog.com/pod…
Look at what happened HipChat, Stride, etc.
From the Matrix side, we're ridiculously happy to have the opportunity to defragment developer chat a bit, and get folks on Gitter natively talking to folks elsewhere on Matrix (including bridged to IRC, Slack, Discord or whatever). The fragmentation of FOSS development chat into proprietary silos a few years back was incredibly depressing, and this is our attempt to put right what once went wrong :) Happy to try to…
So, how long will it take (approximate) to complete the mentioned process ? Also, I think that matrix ecosystem will grow from this move.
We hope to get Gitter natively speaking Matrix in the coming months. It'll probably be a year or so before Element has feature parity with Gitter though :)
Additional topics discussed in our just-released conversation[1] with GitLab and Element leads: 1. What happened to "ChatOps" and why is GitLab divesting in this space? 2. Who contacted whom? What are some details of the acquisition process and negotiations? 3. What does this mean at a practical sense for existing Gitter users? 4. What's going to happen in the next 6, 12, and 18 months? [1]: https://changelog.com/pod…
2. GitLab contacted Matrix.
I think 3. and 4. have answers in https://matrix.org/blog/2020/09/30/welcoming-gitter-to-matri...
> 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…
For me, one shortcoming of gitter is that it has always been tertiary in my pool of chat services. The more tertiary services are accessible through matrix the better, that way I'm less likely to miss notifications.
I don't think there are big downsides, I can't think of anything in the core gitter chat that I would miss when switching to matrix.