[nkantar]

Is this really more important than some rather basic messaging principles Slack is still ignoring?

- No way to ignore/mute users. Yes, I sometimes need to do that even on my team.

- Group DMs inherit notification preferences of channels instead of DMs.

- No visual distinction between "/me says hi" and "_says hi_". (OK, may be minor, but as a long-time IRC user it's quite annoying.)

I can't wait for this threading to introduce the headaches inherent to some users using them and others not.

[okdana]

Some other basic issues i have with Slack:

* Spell-checking is semi-broken on macOS when you have more than one system language specified.

* A few months ago they broke the holding-Shift thing when uploading files.

* The fake Markdown is awful. Aside from the fact that the syntax is just close enough to actual Markdown to be confusing — and i realise that's probably not something they'll ever fix, due to inertia if nothing else — the parser is extremely naïve (maybe based on regular expressions?). Notably, it doesn't support escaping, and it has weird issues with certain special characters (for example, it can't render the string `a|b` as in-line code because it contains a pipe).

* The cost for the paid version is really steep if your project/organisation is on a limited budget. I wish they would introduce a lower-priced tier.

* Maybe they aren't interested in this demographic, but a lot of people really want to use Slack for non-business-related purposes, and they've done nothing really to make that easy in terms of administration/management. Many people with this use case are moving to Discord, which is a shame in my opinion because the Slack client, despite its problems, is still (for now, at least) vastly superior for text-based communication.

* I know it's kind of petty, but they haven't updated the client to support the emoji added since Unicode 8.0 in summer of 2015.

[chaostheory]

Not sure if it's just me but Slack's notifications just aren't good enough. I want something stickier like pretty much every other native IM client that existed before Slack

[DoofusOfDeath]

> The fake Markdown is awful.

+1 on this. I'd be much happier with Slack if they supported Github style markdown, including syntax-highlighting.

I don't understand objections to this based on inertia. The markdown style could be specified on a per-channel basis: traditional or Github-like.

If my team ever moves away from Slack, it would most likely be because of this issue.

[baddox]

Well good, at least the Shift upload thing isn't just me. That's been frustrating.

[nkantar]

Now that I read up on what Shift+upload is supposed to do, I wish it worked.

[nkantar]

Oh, the fake Markdown is indeed awful, I've almost gotten used to that. It's incredible how often I type "something" only to have to press "Up", edit to "something", and "Return". So close, yet so far away...

[tupshin]

Given that none of those things are important to me, and that threaded messaging is important to me, I suspect we have very different answers to that question.

[nkantar]

That's fair. My question was fairly rhetorical, and a bit flippant.

We all have different requirements. I can understand that threading may be important to some, but feel that ignoring users and consistent notification defaults are on the same level.

In fact, seeing as how notifications are already implemented, I see the inconsistency (which has caused me to miss important messages on multiple occasions) as a bug, which should take precedence over a new feature.

But still, clearly many feel differently, and that's OK. :)

[nkantar]

Another thing I completely forgot about: no mention of keyboard shortcuts for threads...