Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Threads in Beta

element.io

Post reply on HN
Print view View original

71–80 of 81 posts

Re: Introducing Threads in Beta

#71

Post by a1445c8b »

alanfranz wrote: post #42
kadoban wrote: post #5

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?

There are times when a conversation that’s important to some participants spontaneously starts in chat and it’s too disruptive to ask less interested (but important) participants to “move it to email.” Suggesting that might cause the conversation to fizzle out which the more interested parties can’t afford.

Re: Introducing Threads in Beta

#72

Post by nkozyra »

heyoni wrote: post #40
nkozyra wrote: post #33

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.

Slack buries threads at the surface level. This is helpful in some situations but can lead to a lot of confusion

Re: Introducing Threads in Beta

#73

Post by jeroenhd »

stevenicr wrote: post #70
jeroenhd wrote: post #23

Earlier quoted context omitted.

Each home server has a room directory. You can rooms in your client (top left in Element, I believe) or you can try browsing this list: https://view.matrix.org/

I really want to make a matrix servers not listed there list.. but I suppose it would have to be broken up into different pages and hosted in different parts of the world for different issues. I have an open to the public (adult public) matrix server that will never make it on that list - and federation is turned off so it wouldn't show up in the rooms lists or whatever of any of those also.

The list contains several NSFW rooms so although federation would probably be the only problem.

A general list that isn't auto-generated through federation might work, but you'd have to put in a lot of manual work to make sure the list is up to date.

Re: Introducing Threads in Beta

#74

Post by godelski »

jeroenhd wrote: post #23
godelski wrote: post #9

How 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.

Each home server has a room directory. You can rooms in your client (top left in Element, I believe) or you can try browsing this list: https://view.matrix.org/

So the problem here is that this is still difficult for discovery. And when I look at some of the rooms all I'm seeing is that users are added and no actual activity.

Re: Introducing Threads in Beta

#75

Post by alanfranz »

kadoban wrote: post #59
alanfranz wrote: post #42

Earlier quoted context omitted.

Why would you use a chat app for conversations spreading over days?

Why not?

Do you usually randomly chat about a topic with multiple people over the course of days, without writing down points and/or making a gist?

Re: Introducing Threads in Beta

#76

Post by alanfranz »

a1445c8b wrote: post #71
alanfranz wrote: post #42

Earlier quoted context omitted.

Why would you use a chat app for conversations spreading over days?

There are times when a conversation that’s important to some participants spontaneously starts in chat and it’s too disruptive to ask less interested (but important) participants to “move it to email.” Suggesting that might cause the conversation to fizzle out which the more interested parties can’t afford.

Threads are a stopgap measure. But the problem is using a chat app for extended-scope conversations.

We don’t have a good way to switch from chats to more forum-like conversations, and email is perceived as too complex (and has other issues in current implementations)

Re: Introducing Threads in Beta

#77

Post by design-material »

replygirl wrote: post #43
sandstrom wrote: post #28

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…

you can enforce this in slack with a toggle

What's the option called for that toggle?

Re: Introducing Threads in Beta

#78

Post by thiht »

What I’d love for threads, in any chat client:

- possibility for the mods to move messages to a thread, as simply as drag and drop. No more « use a thread please »

- possibility for a thread to become a sub-channel, either manually, or automatically if a thread is active for multiple days, or if it’s still active but users need to scroll significantly to see it

- archiving of sub channels manually, or automatically after a time of inactivity

Re: Introducing Threads in Beta

#79

Post by kadoban »

alanfranz wrote: post #75
kadoban wrote: post #59

Earlier quoted context omitted.

Why not?

Do you usually randomly chat about a topic with multiple people over the course of days, without writing down points and/or making a gist?

Over days, yes. Without writing down notes? No. I write notes and you can throw them in slack if they're sharable. I don't really see the issue.

Re: Introducing Threads in Beta

#80

Post by HonestIsNow »

ksala_ wrote: post #39

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…

awesome explanation of a half-broken feature and a job-to-be-done. We're working hard to fix that.
Post reply on HN