Live data from Hacker News

Threaded messaging comes to Slack

slackhq.com

91–96 of 96 posts

Re: Threaded messaging comes to Slack

#91
post #48
post #30

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…

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 n…

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

Re: Threaded messaging comes to Slack

#92
Why not simply have threads be channels that are children of other channels?

This way you discourage branching but allow an unlimited amount of it. And each thread has the same properties and rules as a channel.

All you have to do then is solve the problem of listing the channels in the sidebar, which the user is participating in, in a hierarchical way. A user should be able to leave a thread and it would disappear from their sidebar. Simple.

What's wrong with this model?

Re: Threaded messaging comes to Slack

#93
post #69

IIRC mattermost added this in v3.3.0.

Mattermost team here, thanks for the mention! Mattermost had threaded messaging since 2015, it used to be called "Replies" and we renamed it "Threaded messages" in April 2016: https://about.mattermost.com/mattermost-3-4-7/ If anyone wants to try it out, you can join https://demo.mattermost.com/ Mattermost is an open source, private cloud Slack-alternative. We're "Slack-compatible, not Slack limited" and you'll find a…

hey, can you guys write a native android app? web-embedded is unacceptably slow.

this is a core feature of slack.

Re: Threaded messaging comes to Slack

#94
post #69

IIRC mattermost added this in v3.3.0.

Mattermost team here, thanks for the mention! Mattermost had threaded messaging since 2015, it used to be called "Replies" and we renamed it "Threaded messages" in April 2016: https://about.mattermost.com/mattermost-3-4-7/ If anyone wants to try it out, you can join https://demo.mattermost.com/ Mattermost is an open source, private cloud Slack-alternative. We're "Slack-compatible, not Slack limited" and you'll find a…

No problem, I'm a fan of the product. Been using it since v2.1.

Re: Threaded messaging comes to Slack

#95
post #71

Earlier quoted context omitted.

Slack is the poor mans IRC. The Dropbox of messaging apps. It's easy but if you want to hide your email from public view or customize anything good luck. Slack is notoriously ignorant to customer requests.

Whenever someone compares Slack to IRC I try to imagine my company, where 70% of people are non-technical, using some IRC client as our chat app. There's no way this would happen. Slack was never meant to replace IRC, it was meant to be used at work. Why would you hide your email from your colleagues?

  Why would you hide your email from your colleagues?
..

  using some IRC client as our chat app
Try IRCCloud, it's extremely simple and much better than Slack in almost every way.

Re: Threaded messaging comes to Slack

#96
post #57
post #53

Earlier quoted context omitted.

Any ldap or ad integration?

It would be quite amusing if it couldn't work with AD, considering Zulip is based on Zephyr which is a very old chat protocol/application heavily dependent on Kerberos.

Just FYI, Zulip uses a similar UI model to Zephyr, but doesn't use the Zephyr protocol internally. (For example, Zephyr doesn't really work when one user is behind a NAT)

(I worked for Zulip, and have contributed to the open-source project)

Post reply on HN