Introducing Threads in Beta
element.io
Introducing Threads in Beta
1–10 of 81 posts
Re: Introducing Threads in Beta
#2I 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 spend a lot of time just reading the message.
We need something to improve email experience (where you need forwards, setting up mailing lists is slow, can’t delete/edit, etc) without resorting to a chat app for everything. A better forum-like/nntp, not a better irc.
Re: Introducing Threads in Beta
#3None 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.
Re: Introducing Threads in Beta
#4I 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.
Re: Introducing Threads in Beta
#5I 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 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 messages in the thread most people catch on
2. Slack kind of sucks at notifying you about threads. You mostly have to know to look in the "Threads" thing on the side and not rely on notifications.
Neither of those are that serious or even that intrinsic to threads in chat apps in general.
Re: Introducing Threads in Beta
#6None 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.
Nothing does stop you from having multiple browser tabs open for Element. It is kind of wasteful and awkward though. I agree that this would be useful, though getting to ux nice might be challenging.
Re: Introducing Threads in Beta
#7None 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.
Absolutely. I miss having multiple windows, each with one or more tabs, all respectful of my screen real estate!
With most IRC clients or multi protocol chat programs you could have a couple of important channels always visible on a second monitor, key people you DM a lot in a tabbed window somewhere prominent, active chats open next to your work, and everything else in the main app window, minimised.
Now we have a website (wrapped in an app, if we’re lucky) with next to no layout control. It’s nothing short of a disastrous step backwards.
I’m convinced the recent resurgence of the terminal is partly due to the complete abandonment of GUI applications for most forms of professional computing.
We desperately need a new framework for applications:
- offline first
- local first
- data first
- standardised types and APIs
- as composable as the terminal
- standard controls across all apps
- standard window and document model
- web views considered harmful
- UX and “customer journey” designers considered worse
We were nearly there, then “web 2.0” happened
Re: Introducing Threads in Beta
#8I 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…
Threading makes channels far less noisy for me. Especially the larger the channel is. When is just a few people I don't need threads. But >3 they are great and help organize. The greatest thing about them is also that you don't have to use them!
Slack itself has a large amount of issues beyond this. Notifications (ringing my phone hours after I answered a message or not notifying me at all). Not dropping you into threads for notifications and many other things.
Re: Introducing Threads in Beta
#9How do you all find element channels. I'm interested in trying matrix but I also haven't really found channels I'm that interested in.
Re: Introducing Threads in Beta
#10None 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.
Absolutely. I miss having multiple windows, each with one or more tabs, all respectful of my screen real estate! With most IRC clients or multi protocol chat programs you could have a couple of important channels always visible on a second monitor, key people you DM a lot in a tabbed window somewhere prominent, active chats open next to your work, and everything else in the main app window, minimised. Now we have a w…
> Now we have a website (wrapped in an app, if we’re lucky) with next to no layout control. It’s nothing short of a disastrous step backwards.
This is true of Element, but you can have a Matrix client with any form you like. There already exist several. So it's not the most compelling criticism here IMO, because those who are using Element have chosen it over other options.