15 comments

  • Jim SilvermanJim Silverman, over 5 years ago

    the "email-killer" takes another step toward just actually being email. nice.

    25 points
  • Nicholas MandelbaumNicholas Mandelbaum, over 5 years ago

    I think it's great, we often have long conversations about feedbacks, with several subjects , and I always found it difficult to react on previous messages.

    4 points
  • Guilherme Coelho, over 5 years ago

    Whaat?? So real-time chat is not the silver-bullet that will solve all communication issues in the workplace? Can't believe it

    3 points
  • Renato de LeãoRenato de Leão, over 5 years ago

    We've been discussing this feature for quite a while at my team. It gets really messy when, sometimes, two discussions are happening at the same time in the same channel and boom.. crossroads of replies!

    In my opinion, it will benefit mostly distributed teams.

    I've been working remotely (8h+ timezone away) and it's really hard to keep up with the discussions of the locals (people in office). Specially those long ones with hundreds of replies. When you want to participate, the debate had already ended or people were sleeping or the "thread" is lost in so many cross-messages-replies that you eventually give up. This will keep the thread fresh. Long enough to everyone, independently of their location in the globe, to participate.

    Yes, I'm not talking only about work, those threads normally have proper channels/groups and it's easy to keep up with them (although it will be also great for feedback on designs).

    I'm talking about being part of the everyday life of a team: rants about politics, football, tech nerdery or replying to a cat video with whole thread of cat videos!

    So my a priori opinion is: you did it again Slack! Thanks! Now let's try it out and see how it goes!

    3 points
  • Luca Candela, over 5 years ago

    The inevitable capitulation came and in a form that ignores all the learning previously done by others. Zulip has a much better threading system that works great and it's been a while. Slack should have just copied it wholesale.

    1 point
  • Jrtorrents Dorman , over 5 years ago

    I recently only stared using skack because it was the preferred platform for a project that Im working on and it's a mess!

    1. The onboarding doesn't make any sense! You can't sign in to your account without first joining a channel (perhaps there's a way?) . This makes zero sense! You should be able to sign in to you accound then add channels later.

    2. This is supposed to be an "email killer" yet, the first thing it did was flood my email with notification until I turned it off. Why isn't it off by default?

    3. The interface is jarring, just too much is going on.

    4.If you sign in to the desktop app, you have to manually add all the re-add all the channels. Perhaps I didn't do something right.

    1 point
    • Raphael LoderRaphael Loder, over 5 years ago

      Perhaps there were some misunderstandings: (some things might have changed since I last signed up for Slack, so bear that in mind)

      You can't sign in to your account without first joining a channel (perhaps there's a way?)

      1. The wording is confusing. Channels are conversations between (mostly multiple) people within Teams. I don't know if you misused the term here or I didn't catch the meaning. You don't sign up for "Channels", you sign up for Teams (within these Teams you can manage Channels). These Teams are completely separate and you don't share any information between them, other than that you can use the clients to sign in to those Teams simultaneously and switch between them whenever you choose.

      2. This is understandable. I can't remember that happening to me, but having these e-mail notifications as an opt-in rather than an opt-out made always more sense to me.

      3. I don't really agree with this point. It's really subjective (and it seems you got off on the wrong foot and try to justify disliking it with a rather broad statement). There's certainly a lot more going on than there was at the start, but I only use a tiny portion of the interface (be it mobile or desktop) and found that the rest doesn't get much in the way and is really easy to use once you get to it. But as I said: pretty subjective.

      4. This goes with Point 1: you sign up for Teams separately and of course when you install the client you have to add them one by one (in case you confused Channels with Teams).

      0 points
  • Rachel MerskyRachel Mersky, over 5 years ago

    I'm personally very excited about this. Sure, I agree about the clutter, I think it could be laid out a bit more intuitively, but I've been waiting for something like this. Working within a company with 150+ people, and in channels that span multiple disciplines, it can be difficult to follow multiple threads and find the feedback pertaining to specific questions efficiently and easily. I'm excited to try it out!

    1 point
  • Sam SolomonSam Solomon, over 5 years ago

    Just looking at the concepts, I feel this just adds a bunch of clutter to the interface. I understand the benefits of seeing a specific conversation, but for a real-time chat application, it seems out of place.

    Most of my Slack channels have less than 20 people. Perhaps, this is more of a benefit to larger companies?

    1 point
    • Mick NMick N, over 5 years ago

      I understand your concerns here, for a small team this seems pointless. But I'm a part of a slack that has 75+ users and TBH this feature is quite exciting for that team.

      6 points
      • Lucas LazaroLucas Lazaro, over 5 years ago

        I completely agree, we use Slack with #support-design #support-ops types of channels, multiple project managers can ask for different aspects of multiple projects, so before it would get either messy or would force people to start a multiple conversation with people on a different window. This feature makes the conversation public and able for more people to contribute.

        1 point
  • Jesse DobbelaereJesse Dobbelaere, over 5 years ago

    No threads was really the only reason for our company (200+ people) not to use Slack. We've been using Flowdock for the last couple of years, which has threads. We've been saying that as soon as Slack releases this feature we're gonna switch, and i'm so glad they finally did! Already transitioning...

    0 points
  • Mc DaveMc Dave, over 5 years ago

    Looks like a complicated way to implement a message board. PHPBB does threads much neater.

    0 points
  • Daniel FoscoDaniel Fosco, over 5 years ago

    Looks messy. Let's see how it goes.

    0 points