Live data from Hacker News

Gitter now speaks Matrix

matrix.org

21–30 of 122 posts

Re: Gitter now speaks Matrix

#21
This is a great addition to Matrix. One of the things I really like about Matrix is how matrix.org has an IRC bridge that bridges all of Freenode. It is good to see Gitter getting bridged into Matrix too.

For example, if you want to join Freenode #lisp channel via Matrix, you can do so by joining #freenode_#lisp:matrix.org. Here is a direct Element web client URL to it, in case you want to try it now: https://app.element.io/#/room/#freenode_#lisp:matrix.org .

Element (previous known as Riot) web client is a great way to get started with Matrix without having to install anything. You have to create an account of course but after that it is pretty straightforward. The fact that all of Freenode (and now Gitter) is available on it makes it like one big IRC bouncer. Moreover, this is all distributed and decentralized!

Here is another safe Matrix room to try out and experiment with: https://app.element.io/#/room/#spxy:matrix.org . Most of us here are from Hacker News. We talk about computer science and mathematics here. Common Lisp and Emacs are being discussed these days. Say "hi" if you join it! :)

Re: Gitter now speaks Matrix

#22
If anyone on the Gitter/Matrix dev team is reading the post comments, here's a question for those who already use both platforms:

If I have an account on Matrix, but I also sign into Gitter with Github credentials, how would I go about merging the two accounts (without loss of data)?

Re: Gitter now speaks Matrix

#23

Earlier quoted context omitted.

A lot of people, including me, dislike threading in Slack. It breaks the algorithm for reading new messages. I use it when teammates do, and acknowledge it's useful sometimes, but I would prefer not to have that feature. Discord also does not have threads. I've heard some complaints about it, but not many. Threads in Zulip seem to change it into a different kind of app. I don't see how the Slack workspaces that I've…

Discord has a feature (recently added?) in which you can reply to something -- it gets miniquoted above your reply. It does a good job of 'flattening out the tree'.

Element appears to have the same thing right now

Re: Gitter now speaks Matrix

#24

If anyone on the Gitter/Matrix dev team is reading the post comments, here's a question for those who already use both platforms: If I have an account on Matrix, but I also sign into Gitter with Github credentials, how would I go about merging the two accounts (without loss of data)?

I don’t mind that being an option, but I would not want that happening automatically.

Re: Gitter now speaks Matrix

#25
post #3

That was impressively quick. Looking forward to Github/Gitlab repository rooms and activity integration. In the acquisition announcement they also mentioned threading though, which is the most important feature Element is missing for me. Without it I'm very hesitant to use it in a professional setting. I do hope that threads will look much more like Zulip rather than Slack (which is a mess), or offer different view m…

Matrix now has two flavours of threading defined and implemented as we experiment with the different approaches: label-based threading in MSC2326[1] (i.e. "filter this room to only show msgs tagged #foo"), and full-blown free-form HN/Reddit/NNTP/SMTP/Twitter style threading in MSC2836[2]. The former is closer to Zulip, and is implemented in Synapse. The latter is closer to HN, and is implemented in Dendrite[3][4].

Clientwise, Element supports neither so far, but we're experimenting with the HN-style threading in a dedicated playground called Cerulean[5]. The idea is to get it working well there, and then figure out how to merge it most effectively into Element. So: it's not ready yet, but it's getting tantalisingly close. We'll probably start hosting a demo version of Cerulean next week so folks can play along and see how it feels :)

[1] https://github.com/matrix-org/matrix-doc/blob/matthew/msc232...

[2] https://github.com/matrix-org/matrix-doc/blob/kegan/msc/thre...

[3] https://github.com/matrix-org/dendrite/pull/1589

[4] https://github.com/matrix-org/dendrite/pull/1596

[5] https://github.com/matrix-org/cerulean

Re: Gitter now speaks Matrix

#27

If anyone on the Gitter/Matrix dev team is reading the post comments, here's a question for those who already use both platforms: If I have an account on Matrix, but I also sign into Gitter with Github credentials, how would I go about merging the two accounts (without loss of data)?

We don't have account merging yet, as while Matrix can see all of Gitter, we're not exposing the entirety of Matrix into Gitter (mainly because it'd cause the Gitter AWS bill to go through the roof :P). Once Gitter becomes a pure Matrix client, though, you'll automatically be able to use your Gitter.im homeserver credentials to access Matrix, and with account portability (MSC2787[1]) there /may/ end up being a way to combine two existing accounts into one.

Re: Gitter now speaks Matrix

#28

oh this is huge. and right in time for the slack acquisition ! gitter fixes one of the biggest issues with matrix - the product/ux/ui. one thing im not sure of is the conscious decision to deprecate mobile apps and instead recommend mobile web. https://gitlab.com/gitterHQ/webapp/-/issues/2281 is that a strategic decision ? because this wont be a pleasant experience is potentially a massive blocker for any type of ser…

We're not recommending mobile web; rather than replacing the native Gitter mobile apps with the Gitter mobile webapp, we're instead recommending folks move to native Matrix mobile clients like Element (or mobile web Matrix clients like Hydrogen, if they prefer).

Re: Gitter now speaks Matrix

#30
post #13

"In the medium/long term, it’s simply not going to be efficient for the combined Element/Gitter team to split our efforts maintaining two high-profile Matrix clients. 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 - we expect to upgrade the deployment on gitter.im to a Gitter-customised version of El…

To be 100% clear: we are not going to shelve the Gitter codebase until Element (or other Matrix clients) have total parity with it. And once we do, we'll replace the current Gitter codebase with a Gitter-branded version of Element, and make sure it's configured so all the Gittery stuff works as you'd expect... while also benefiting from all the work we're pouring into Matrix and Element. So, I'd see it more like Gitter sprouting E2EE, VoIP, widgets, reactions, video conferencing, open standard API, etc, rather than "gitter being shelved" :D
Post reply on HN