Earlier quoted context omitted.
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]. Cl…
I realize it must be annoying to have this topic brought up every time Matrix is mentioned, so thanks for the update! Nested threading could enable some interesting use cases, but I think for many contexts a single nesting level would be better though. Is the current plan to allow customization via room settings?
Gitter now speaks Matrix
51–60 of 122 posts
Re: Gitter now speaks Matrix
#52Earlier quoted context omitted.
So...could I write a gateway that provides functionality for threads to be pulled in from HN/Reddit/NNTP/SMTP/Twitter (MSC2836)? Think Epiverse [1] within Matrix and its clients. [1] https://epiverse.co/
Epiverse appears to be a browser extension that automatically shows you Reddit and Hacker News threads about the page you're visiting. Does it send every URL you load to a third-party server to provide this functionality?
Re: Gitter now speaks Matrix
#53Earlier quoted context omitted.
So...could I write a gateway that provides functionality for threads to be pulled in from HN/Reddit/NNTP/SMTP/Twitter (MSC2836)? Think Epiverse [1] within Matrix and its clients. [1] https://epiverse.co/
Epiverse appears to be a browser extension that automatically shows you Reddit and Hacker News threads about the page you're visiting. Does it send every URL you load to a third-party server to provide this functionality?
Re: Gitter now speaks Matrix
#54The ecosystem of a multitude of various chat apps is daunting and confusing. I've been finding that I'm spending more time talking and thinking about chat programs rather than actually doing anything valuable. It's kind of like how ham radio operators almost exclusively talk about ham radio on ham radio (when not talking about weather and personal ailments, lol).
Re: Gitter now speaks Matrix
#55This is amazing! Side note, there seems to be a typo "would be to have got Gitter". Also, I'm curious what the plan is to reconcile Gitter's one room per repo model with Matrix's anybody-can-create-any-room - in the long term, is the plan to keep gitter.im rooms restricted to matching repos? Or (post gitter-skinned-element) will people eventually be able to create arbitrary rooms on the gitter homeserver?
This isn't exactly elegant English, but I think it's structurally correct. In US English you might say "gotten Gitter", i guess.
> Also, I'm curious what the plan is to reconcile Gitter's one room per repo model with Matrix's anybody-can-create-any-room
You can already create non-repo rooms in Gitter, so this one's already solved. For instance, I just created https://gitter.im/matrix-org/matthew-test (with no matching repo) :)
Re: Gitter now speaks Matrix
#56Earlier quoted context omitted.
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).
well you do https://gitter.im/apps > The dedicated Android/iOS apps are no longer recommended and may be officially deprecated in the future. For mobile, we recommend using the mobile web version in your browser.Our efforts are focused on the webapp which is the backbone of the mobile/desktop apps but mainly focused on the web experience. There are a number of bugs in these desktop/mobile clients and they spread the…
Re: Gitter now speaks Matrix
#57Gitlab comes with an easy Mattermost integration. Therefore, we use Mattermost in our team instead of Gitter. What's the status of Mattermost vs. Matrix? I found https://about.mattermost.com/matrix/ but this seems to be ... irony ;-)
Re: Gitter now speaks Matrix
#58Earlier quoted context omitted.
I realize it must be annoying to have this topic brought up every time Matrix is mentioned, so thanks for the update! Nested threading could enable some interesting use cases, but I think for many contexts a single nesting level would be better though. Is the current plan to allow customization via room settings?
We haven't got as far as figuring out how to advertise/negotiate the threading flavour of a given room. It'd suck if half the people in the room are trying to use it like IRC and the other half are trying to use it like HN tho!
Re: Gitter now speaks Matrix
#59Great news! Very quickly done, which kind-of makes me suspicious... One thing I did already observe is that I was able to send a message to a closed Gitter room via my Matrix account, although I couldn't see other people's messages.
Re: Gitter now speaks Matrix
#60That 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…
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…
Quite simply: you don't know what you are missing.
I was sceptical at first as well, but having the ability to branch off into separate sub-topics while still maintaining easy visibility is extremely nice for organizing conversations and catching up on things you missed in busy channels.
The nice thing is: you can just use flat channels where appropriate, or just ignore the nested topics and read a channel as a regular continuous stream.
It's incredibly conducive to long-form discussions and organizing information, while still retaining the casualness of a chat when required.