51–60 of 81 posts
None of these "innovative chats" that already use a browser to display them can even come up with the idea of tabs . Nope, they all insist on keeping everything inside a single window. So even if you have thread "for better communication with no noise", it still gets lost in all other threads, and they come up with workarounds like a dedicated page for threads etc. Just give me tabs, damnit.
Are there still plans for Zulip-style threads? https://github.com/matrix-org/matrix-spec-proposals/pull/232...
Yes. The plan is for Matrix to support both arbitrarily deep threading (like https://matrix.org/blog/2020/12/18/introducing-cerulean does) - as well as Slack/Discord style threading. They have very different semantics; we added Slack style threading to Element first for familiarity and bridging with Slack, but I can’t wait for fully branchy threads to be in production too for bridging to Zulip (or HN ;P)
What I'd prefer is the Twist-style threads (Zulip may also have them), where every room/channel must contain only topics/threads, and those topics have a title/description, and any messages in them are 1-level (no nested threading). It looks like this: #office [room/channel] * Lunch [thread/topic] - Anyone wants to grab lunch today? [message] - Sure, I'll join! [message] - Me too! [message] * Printer doesn't work [th…
The hope is to add it later. The first cut is plain Slack-style threads, but we have MSCs for zulip/twist style threads like https://github.com/matrix-org/matrix-spec-proposals/pull/283... which will get built out as soon as we can. Fun fact: the design for Element’s current threading is from a former Twist designer; make of that what you will :)
Does Zulip support nested threads?
I think threading in chat apps is a terrible idea. It’s a way to merge email and chat, but chat apps like Slack aren’t really suited for such replacement imho. Why threading if there’s not much noise? And if the noise is too much, maybe a public chat is not the best idea. on Slack, navigating a channel between “main” messages and thread messages is a nightmare, and since “main” messages are not just a subject, you sp…
I would say it depends on the implementation. Slack is pretty horrible, but Zulip is the best thing ever.
Slack threads are a tangent to a point, an aside to something said in the main timeline. Zulip threads are like forum threads, a discussion of some particular topic.
What I'd prefer is the Twist-style threads (Zulip may also have them), where every room/channel must contain only topics/threads, and those topics have a title/description, and any messages in them are 1-level (no nested threading). It looks like this: #office [room/channel] * Lunch [thread/topic] - Anyone wants to grab lunch today? [message] - Sure, I'll join! [message] - Me too! [message] * Printer doesn't work [th…
The hope is to add it later. The first cut is plain Slack-style threads, but we have MSCs for zulip/twist style threads like https://github.com/matrix-org/matrix-spec-proposals/pull/283... which will get built out as soon as we can. Fun fact: the design for Element’s current threading is from a former Twist designer; make of that what you will :)
Earlier quoted context omitted.
Nesting was around pretty early on, but yeah. I think what all of these platforms are discovering is that we figured out some pretty intuitive patterns early on and are on a constant loop of wanting to do something different before eventually realizing this and reverting. There's a hybrid wherein you keep references to a branch in a thread but you still display a flat discussion. If you choose to follow the branch yo…
Which slack does already.
Threads are probably a good idea, but as many people have pointed out I still have to find an app that have a good implementation of them. Most of my experience is with Slack so maybe Twist/Zulip are better at this. * I hate threads in direct messages. Please, Slack, just give people a nice way to quote messages instead - which in my experience is mostly what people want. Right now it's a mix of copying a message and…
Earlier quoted context omitted.
I don't really see the issue with it. In Slack, we have a channel for our team. In that channel we have conversations, often more than one at a time, spread out over minutes to days. Why shouldn't each conversation have its own separate thread? The only real problem(s) I have with threads in Slack are: 1. some people suck at remembering to reply in thread. This isn't too serious though, once there's more than 2 messa…
Why would you use a chat app for conversations spreading over days?
Earlier quoted context omitted.
The hope is to add it later. The first cut is plain Slack-style threads, but we have MSCs for zulip/twist style threads like https://github.com/matrix-org/matrix-spec-proposals/pull/283... which will get built out as soon as we can. Fun fact: the design for Element’s current threading is from a former Twist designer; make of that what you will :)
Does Element have discord-style replies? This is the biggest feature missing in slack for me. Being able to quickly reply to a particular message that might be 2-3 messages behind goes a really long way in being able to maintain multiple flows of a conversation