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

Threaded messaging comes to Slack

slackhq.com

Post reply on HN
Print view View original

71–80 of 96 posts

Re: Threaded messaging comes to Slack

#71

Post by arnvald »

myowncrapulence wrote: post #50
allover wrote: post #33

Earlier quoted context omitted.

Despise/tolerate/mess? The basic offering is a simple chat client with 'channels' and an easy signup/invite flow afaict.

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?

Re: Threaded messaging comes to Slack

#72

Post by brazzledazzle »

pfarnsworth wrote: post #67

What I want more is columns in Slack so I can see conversations in multiple rooms without having to click back and forth on them whenever a new message pops up. It's annoying that I can only see one at one time when I have so much screen space.

They used to have scaling issues (maybe still do for certain userbase sizes) so it might not be feasible for them to effectively double the amount of real-ish time updates.

It would be really handy for informational channels where generally you're just interested in reading updates, not replying. Something like that could reasonably live in the right-hand sidebar. Taken a step further, it would be really cool to be able to specify an official informational/status sidebar channel to be paired with your channel. For example: a team channel with a build status channel linked to it by default.

Re: Threaded messaging comes to Slack

#73

Post by bigiain »

lowglow wrote: post #40
bigiain wrote: post #39

Earlier quoted context omitted.

Say, that's an interesting new wheel you're inventing there! ;-) https://www.jwz.org/doc/threading.html (And I doubt jwz was the first smart guy to devote time to that particular problem too...)

His redirect is hilarious.

Oh yeah - I'd forgotten about that. Maybe copy/paste that url instead of clicking it... ;-)

Re: Threaded messaging comes to Slack

#75

Post by nkantar »

tupshin wrote: post #49
nkantar wrote: 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…

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.

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

Re: Threaded messaging comes to Slack

#76

Post by nkantar »

okdana wrote: post #48
nkantar wrote: 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…

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

Re: Threaded messaging comes to Slack

#77

Post by nkantar »

baddox wrote: post #55
okdana wrote: post #48

Earlier quoted context omitted.

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…

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

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

Re: Threaded messaging comes to Slack

#79

Post by wapz »

spilk wrote: post #78

Maybe I'm just overly paranoid but I've never understood the appeal of Slack - I personally don't want to ship all of my internal proprietary business communications offsite to a third party.

I think it really depends on what your team needs to discuss, but from my slack chats we don't discuss any business-breaking proprietary intel. If there's something important a face-to-face meeting is used or video chat (but that's also through hangouts)
Post reply on HN