News for hackers. Stuff that matters.
Re:Gitter now speaks Matrix by the_duke on Monday December 07, 2020 @12:56PM (#25334807)
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 modes. Zulips nested channel concept is a game changer.

(as I understand it, the protocol already has the required plumbing)

Re:Gitter now speaks Matrix by Arathorn on Monday December 07, 2020 @01:49PM (#25335567)
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 by alexvoda on Monday December 07, 2020 @04:19PM (#25337695)
Does Matrix support linearly directed imageboards (e.g.:4chan) style threading?

In 4chan threading is done by linking the between posts using the post id permalink (1). This is aided by the UI which allows you to hover over the listed ID and see parents or children. This results in being able to respond to multiple posts in a single post. This means that instead of tree structured threading, DAG style threading is possible. The second consequence is that by default posts are displayed linearly, like an IRC discussion. This linear display results in unlimited nesting depth. Nesting is not dependent on indentation.

(1) https://www.4channel.org/faq#quote

Re:Gitter now speaks Matrix by toomuchtodo on Monday December 07, 2020 @02:06PM (#25335811)
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/

Re:Gitter now speaks Matrix by Arathorn on Monday December 07, 2020 @02:12PM (#25335876)
Yup. Can't wait for someone to implement a Matrix-powered Disqus clone!
Re:Gitter now speaks Matrix by vlmutolo on Monday December 07, 2020 @02:37PM (#25336191)
Wow, it would be really, really interesting for a blog to offer a Matrix room as a "comment section". If you didn't care about threading, you could probably do something like that even today.
Re:Gitter now speaks Matrix by Arathorn on Monday December 07, 2020 @02:48PM (#25336352)
https://matrix.org/blog/2020/09/15/gsoc-report-html-embeddab... was a GSOC project this year which heads in that direction. Meanwhile Hydrogen has been built to be embeddable (https://github.com/vector-im/hydrogen-web). And Gitter of course has http://sidecar.gitter.im/.

But nobody has fully packaged one up as FOSS Disqus/Intercom/etc alt yet. It's a huge and easily-fillable gap in the Matrix ecosystem :)

Re:Gitter now speaks Matrix by andrewperry on Tuesday December 08, 2020 @08:22AM (#25344681)
We've been working on some Web Components that use the js sdk to talk with matrix but have been wondering if we should spend time looking at how the react sdk could be implemented in this use case assuming it would better handle encryption etc... although I think I read recently that the js sdk also handles encryption - but we'd need to add UI for verification to access encrypted rooms which seems likely to be a pain across browser sessions... there's also an issue as to which websites you might trust to share your matrix user token with to post on your behalf (but will check out Hydrogen to see how it handles this).

So thinking out loud, for a disqus clone - sticking to unencrypted rooms and web components could be the way to go! Thanks for the GSOC and Hydrogen links - will check them out!

Re:Gitter now speaks Matrix by mxuribe on Monday December 07, 2020 @08:38PM (#25340517)
That can definitely be done today: just point a link to a public matrix room...well, the participants would need an account associated to a homeserver first in order to interact...but that's no different - conceptually - than needing to have a disqus account. The benefit of course is that their account can be associated to their __own__ homeserver! In fact, i do this already on my website; though for general contact (like a poorman's contact form), rather than a comment section for blog posts - but the approach works for either perspective.
Re:Gitter now speaks Matrix by SulfurHexaFluri on Monday December 07, 2020 @03:50PM (#25337319)
I wonder how that would work performance wise since I assume comments sections on blogs are loaded many many more times than they are edited so you would want some super fast caching on it.

I guess anything is possible with custom code though.

Re:Gitter now speaks Matrix by mathnmusic on Monday December 07, 2020 @05:09PM (#25338332)
You know what would be a great goodwill-building move from Github and Microsoft? Them running a Matrix server instance and provide a chat room for each Github repo. This is what Gitter used to offer. Federation allows even competitors to interoperate.
Re:Gitter now speaks Matrix by andrewperry on Tuesday December 08, 2020 @08:18AM (#25344645)
Yes, I was actually just looking at it this week!
Re:Gitter now speaks Matrix by paulcarroty on Tuesday December 08, 2020 @07:05AM (#25344181)
There's https://github.com/42wim/matterbridge, supports Reddit/Matrix and many more plus API for extensions.
Re:Gitter now speaks Matrix by toomuchtodo on Tuesday December 08, 2020 @01:01PM (#25349008)
Wow, thanks so much for sharing this!
Re:Gitter now speaks Matrix by pbronez on Monday December 07, 2020 @02:47PM (#25336317)
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 by the_duke on Monday December 07, 2020 @02:29PM (#25336078)
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?

Re:Gitter now speaks Matrix by Arathorn on Monday December 07, 2020 @02:49PM (#25336363)
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 by inputmice on Monday December 07, 2020 @03:11PM (#25336704)
Re:Gitter now speaks Matrix by benatkin on Monday December 07, 2020 @01:17PM (#25335117)
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 used heavily would work with it. There are about 15 channels in my sidebar. Making them nested would turn it into 75, assuming 5 threads per channel. Perhaps there wouldn't need to be as many top-level channels with Zulip threads, but it makes it into a whole different paradigm. They are also missing Slack-style threads. I don't think it would be good to adopt it.

Re:Gitter now speaks Matrix by eXpl0it3r on Monday December 07, 2020 @01:35PM (#25335390)
I like threads a lot in the way we use it. With 60+ people in one channel, being able to ask a question and get answers in the thread, while not spamming the channel with replies and potentially interweaving multiple question & answer "threads" is really useful.
Re:Gitter now speaks Matrix by climb_stealth on Monday December 07, 2020 @03:46PM (#25337262)
Threads in Slack are useful but the implementation is pretty bad. For example you don't see new responses in a visible thread until you click the button for more messages. It makes them really frustrating to use. Slack does a lot of things really well which makes the pain of using threads even worse.
Re:Gitter now speaks Matrix by OJFord on Monday December 07, 2020 @09:00PM (#25340715)
I also wish there wasn't 'sharing', or at least not to the same channel, so that there's one clear way for the 'continue earlier topic' use case.

Having said that, there's also 'reply to thread and also share to channel', making it even worse. I think that one's the closest Slack has to fixing threading's problems though - if you're aware of it being a potential issue, you can at least highlight it.

It'd be good if there were an 'active thread(s)' thing that appeared on the right side or something (at the bottom of what is the the thread panel when one's open, I'm imagining though. Easy to ignore, but when you're checking if there's new messages in your main channel you'd also see if there were new thread activity.

Re:Gitter now speaks Matrix by endgame on Monday December 07, 2020 @05:18PM (#25338453)
And for some boneheaded reason, you can't /collapse in threads, so if you have colleagues who like both threads and gifs, you're stuck.
Re:Gitter now speaks Matrix by the_duke on Monday December 07, 2020 @03:18PM (#25336830)
> I don't see how the Slack workspaces that I've used heavily would work with it.

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.

Re:Gitter now speaks Matrix by benatkin on Monday December 07, 2020 @09:24PM (#25340888)
Well I'll probably never know unless I join a team of 10+ that happens to use Zulip. I played with it on my own for about an hour.
Re:Gitter now speaks Matrix by benhurmarcel on Tuesday December 08, 2020 @06:37AM (#25344037)
My company uses Google Chat, which isn't great but has threads. It would be unusable without that feature, some rooms have thousands of members.
Re:Gitter now speaks Matrix by Xylakant on Monday December 07, 2020 @01:30PM (#25335329)
Zulip threads (topics) are fundamentally different from slack threads.

TL;DR Slack threads are an after-thought add-on, Zulips topics are a first-class citizen.

Slacks threads can branch of at any point from any message in a channel - if you miss the start of the thread message, it disappears unless someone cross-posts to the channel or mentions you. This is by far the biggest problem I have with slack threads.

Zulip organizes into streams and topics, streams being roughly equivalent to channels and topics similar to threads. However, unlike slack, every message must live in a topic. Topics that have seen a message lately bubble to the top, topics that don't see activity fall to the bottom. You can still see the full stream in chronological order, but messages are grouped by and visibly marked with the topic they belong to. This makes it much easier to both follow a stream and still mentally follow multiple conversations in the same stream.

Re:Gitter now speaks Matrix by yawgmoth on Monday December 07, 2020 @01:43PM (#25335470)
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'.
Re:Gitter now speaks Matrix by Kinrany on Monday December 07, 2020 @04:43PM (#25337992)
Telegram also shows all the replies to a given message as a separate chat, effectively turning messages into Reddit-like trees.

It's half-baked, but it seems like a great alternative to regular presentation: linear history, but filterable.

Re:Gitter now speaks Matrix by pbronez on Monday December 07, 2020 @02:48PM (#25336333)
I find this to be a critical feature in long-running threads. I use it extensively in WhatsApp
Re:Gitter now speaks Matrix by boogies on Monday December 07, 2020 @01:48PM (#25335553)
Element appears to have the same thing right now
Re:Gitter now speaks Matrix by ptman on Tuesday December 08, 2020 @06:47AM (#25344098)
replies have been a thing for quite a while in matrix
Re:Gitter now speaks Matrix by ttsda on Monday December 07, 2020 @01:30PM (#25335331)
I think threads, used sparingly, are nice. They're good to have semi-private messages, so you can keep the more irrelevant conversation that would normally go to PM public and searchable, while not spamming the channel. They're also good for support channels, to have a thread per support message.
Re:Gitter now speaks Matrix by cpuguy83 on Monday December 07, 2020 @02:28PM (#25336064)
Threading is the one thing I actually kinda like in Teams.
Re:Gitter now speaks Matrix by rkangel on Monday December 07, 2020 @04:08PM (#25337556)
I actually think that the MS Teams implementation of threads is the best.

The problem with the Slack implementation is that it's not the default. You have to understand it to use it, and you have to have an organisational culture that pushes people to use it. Otherwise you end up only occasional threads, and mostly you're back in in the classic Slack '200 messages since you last visited, only 10 of them are of interest, but you have to read everything to find them' situation.

I like the Zulip version, it is automatically threaded but personally I had a slightly silly problem - you had to think of a topic name. It's a bit like the subject line of an email, except that you don't want it to be as long. This increases the friction slightly and you inevitably end up with a lot of messages going in one topic called something like 'general' when people can't think of a suitable topic name. I haven't used Zulip as intensively as the other two though, so maybe that problem goes away (or maybe it gets worse).

Teams is a lot like Zulip. Everything is in a thread automatically, but you don't have to name it, you just start a new 'conversation'. It works pretty organically, and it works by default without any 'culture' needed. You can give a thread a title if you want, but you don't have to. A bonus of the structure of Teams is that private messages (as supposed to Team channels) are just are a normal sequence of messages like Slack or anything else, because that's what you want. Teams is a memory hog and sluggish to use, but I do think they got that bit of the user experience right. Like many companies we had enforced, hurried massive increase in usage of Teams in March, and it has worked pretty seamlessly.

Re:Gitter now speaks Matrix by unicornporn on Tuesday December 08, 2020 @01:31AM (#25342514)
Threads in Teams? I use it daily and have not noticed that feature. How? In the desktop client I can't even properly quote.
Re:Gitter now speaks Matrix by rkangel on Tuesday December 08, 2020 @05:41AM (#25343735)
In a normal Team channel (i.e. not a chat message) when you press 'New conversation' you type a message and then people reply to that. That is a thread. The fact that you didn't even think of it as one I take an indication how seamless it is.
Re:Gitter now speaks Matrix by StavrosK on Monday December 07, 2020 @04:13PM (#25337627)
I'll second Zulip, though I think the message view and "zooming in/out" they implemented is just as much of a game changer as the threading model.
Re:Gitter now speaks Matrix by ducktective on Monday December 07, 2020 @12:57PM (#25334819)
Can you explain a bit more on "threading" and its relation to a chat service? And why Zulip's implementation is better?
Re:Gitter now speaks Matrix by toyg on Monday December 07, 2020 @01:30PM (#25335333)
He’s talking of threads as in “email threads”, not “process threads” - i.e. indentation and grouping of messages and replies.
Re:Gitter now speaks Matrix by SulfurHexaFluri on Monday December 07, 2020 @03:55PM (#25337385)
Its when IM has a reply feature so you can "reply" to a message sent a little while ago and it quotes the message on the top of yours and usually you can click the message to scroll up to it.

Essential for group chats and still useful for DMs.