# Slack is introducing threaded messaging later this year
**URL:** https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512
**Category:** Feature
**Created:** [April 13, 2016, 4:41pm UTC](https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512 "2016-04-13T16:41:44Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@BCHK](https://meta.discourse.org/u/BCHK)
#### Post date: [April 13, 2016, 4:41pm UTC](https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512/1 "2016-04-13T16:41:44Z")
I find this announcement interesting and wonder if its becoming more like Discourse?.. Your thoughts? Any opinions whether this is relevant at all to Discourse?
> **[Slack is introducing threaded messaging later this year](https://www.theverge.com/2016/4/13/11418594/slack-threaded-messaging-chat-app-feature)**
>
> The messaging app is adopting a hallmark of email
---
### Author:  [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [April 13, 2016, 5:33pm UTC](https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512/2 "2016-04-13T17:33:34Z")
It’s interesting but I have to see how the feature looks for myself before I can really comment on whether it’s similar to Discourse. It doesn’t exactly sound like it from that description though.
---
### Author:  [@holden](https://meta.discourse.org/u/holden)
#### Post date: [April 13, 2016, 5:40pm UTC](https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512/3 "2016-04-13T17:40:12Z")
I have to agree with @eviltrout, this doesn’t sound like Discourse at all.
---
### Author:  [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [April 13, 2016, 5:45pm UTC](https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512/4 "2016-04-13T17:45:00Z")
It’s just a convenience feature, nothing major. I doubt they’ll take it much further than “you can now more easily reply to an older message”. Whatever they come up with, I hope Mattermost will copy it, because I’m not very happy with their current style of threaded messaging.
---
### Author:  [@alefattorini](https://meta.discourse.org/u/alefattorini)
#### Post date: [April 13, 2016, 7:48pm UTC](https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512/5 "2016-04-13T19:48:08Z")
Are you using Mattermost? Any feedback?
---
### Author:  [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [April 13, 2016, 8:38pm UTC](https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512/6 "2016-04-13T20:38:40Z")
Nah, I merely tried it out for a quick evaluation a while back. It’s _very_ similar to Slack, which is another way of saying it’s a very impressive app.
Main set back as far as I’m concerned is that their hosting service (don’t wanna deal with self-hosting) isn’t targeting small to medium businesses yet; they only deal in Enterprise plans.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [March 14, 2017, 11:50pm UTC](https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512/7 "2017-03-14T23:50:26Z")
We have tried the Slack threading and it is _terrible_.
IMNSHO of course.
---
### Author:  [@wscott](https://meta.discourse.org/u/wscott)
#### Post date: [March 16, 2017, 12:56pm UTC](https://meta.discourse.org/t/slack-is-introducing-threaded-messaging-later-this-year/42512/8 "2017-03-16T12:56:34Z")
It never caught on, but I like [Zulip’s](https://zulip.org/) threading model better.
Every message is in a channel and has a one-line topic or subject line. If you reply to a message, it keeps the topic of the parent. If you just send to the channel it keeps the last topic. You can manually change the topic of your message.
The net result is that the default view of a channel shows all messages from all topics in time order, but you can click on one topic to narrow the view to just that conversation. Seems useful, but I never used this on a busy server to see how it works in practice.