Message Threads

評論

581 條評論

  • Ricky

    Bump this

    Have quite experience with Slack and MS Teams. Threading in Slack is just nuts to keep chat tidiness (MS Teams has it only in limited within posts, but not in classic chat) and I really miss this feature on Discord as threading just feels like next gen in chat for large groups and communities. People can comment on specific post/topic without bloating the channel and this is especially true higher the amount of active people you have in channel, it becomes greatly disorganized

    Reply feature is for sure useful, but if you miss the time of discussion and came later? Man that's where mess starting to happen, now since chat is chronologically sorted (logically) your reply to older post is now all of a sudden inside different active topic and that's a mess

    Being a developer I know this is may not be an easiest feature to implement, but also not that hard either... and having such feature can make Discord stand up even more and look how many people are interested, it's not really negligible amount of people I believe

    You can do it!

    0
  • igrir

    It would be a massive headache to develop, but... I'd like this feature please :D

    0
  • TrickyBricks

    100% need this feature. Discord is so good in so many ways. It's odd that this important feature is being treated like such a non-important after thought.

    0
  • treszy

    +1

    0
  • Aids

    please 

     

    0
  • An

    bump

    0
  • Iria

    Agree

    0
  • Achel

    I didn't understand why they still not maked it. THIS IS SO IMPORTANT, Hear us please

    0
  • Vicente Malonda

    Another vote for threads!

    0
  • Maria de la Puente

    Yes please!!! I totally support, I even beg for this feature!

    0
  • Sergio J Ramos

    We really need to have threads in Discord, it's the number one problem we face.
    We are a startup community with over 200 people and it is very difficult to have a conversation without getting lost.

    0
  • Mar Colino García

    I also vote for this feature

    0
  • jublin

    Adding in my vote!

    0
  • intsurrection

    This please!!

    0
  • lietu

    When I'm not willing to dedicate an entire screen to a chat app those side panels don't really work, they clutter up the thing and become so tiny that I can't really read reasonable amounts of anything in the main view or the sidebar.

    -1
  • lietu

    Oh and considering they're not willing to add an option to disable the Nitro gift -box, they might just decide to force threads on everyone as well.

    -1
  • 255

    Why not just message under them?

    -1
  • rayanon

    I have an idea - why not have quoted replies (Whatsapp like), if implementing threads is becoming a challenge?

    My assumption is - it is hard for the Discord team to implement threads because the current data model doesn't account for that. And changing it across the entire stack, updating all the clients can prove to be very difficult and challenging (maybe almost impossible). Hence, the delay on taking a decision on threaded conversations.

    In this case, atleast the ability of quote a reply helps a lot in the UX. When I read someone's reply if its quoted, I would what exactly they are talking about and I can click on the quoted message to go/scroll to the original message. I think this feature would go a long way in helping reading longer, threaded conversations. This feature would be very useful for programming communities, where longer conversations (spanning days) are common.

    -1
  • oreanger

    You can probably just quote the message and tag the person....

    -1
  • mike yaworski

    ^

    It's not about being "fast enough". It's about having to specify context in your message that is a reply to something which happened hours ago, or before a series of other messages. You're just attaching a context to your message.

    Not getting notifications for a conversation you're not interested in is separate problem I suppose. The problem I have with Slack threads is that it's cumbersome to browse and would completely ruin the flow of discord (everything would be collapsed). Flowdock, on the other hand, does not interrupt flow and pretty much every message can be marked for a specific thread. In practice, people don't use Slack threads.

    The other thing is that if you're just watching a thread, but then the thread is done for a few days and someone adds more messages to it, as a reader, you have to go back into that collapsed thread and check for new messages. In Flowdock, the last message in the thread will appear in chat and it's like the thread is reopened for readers as well.

    Definitely pros/cons, but I've found Flowdock to be better. Perhaps the threading system could follow Flowdock's fundamentals and then add in an option to mute specific threads, thereby collapsing them, not spamming your feed and not notifying you of them.

    This is how you're supposed to have a conversation btw. Not throwing in sneak disses like "not fast enough to keep up".

    -1
  • David Song

    bump

    -1
  • David Song

    bump

    -1
  • Cpt_silverfox

    I want to chime in support for threads HOWEVER I think the way slack handles it would be less than ideal. I would encourage you to look at how Twistapp does threads. Basically threads as first-class citizens.

    -2
  • Juliano R4010

    No one from discord read this. this board is useless. I'm off.

    -2
  • Val (trickycrayon)

    KramRM, unless I'm understanding, that doesn't solve the "constantly being notified about conversations I'm not a part of" aspect like Slack-style threading would.

    -2
  • Vadorequest

    Commenting for commenting is not a good move. Better just upvote if you need the feature but don't have any better proposition than what's already said in the main post. Keeping noise at minimal will both help them review the thread (feature details, etc.) and avoid spamming all those following the issue. Cheers!

    -3
  • mike yaworski

    If any devs are looking at this, please look into Flowdock's threading system (as opposed to Slack's). Flowdock has superior threads IMO and they would be much less UI work. Basically adds color thread indicators beside messages and your reply will be in the same thread color. You can open the thread in a side panel to see just that thread.

    -3
  • mike yaworski

    I just wanted to jump in and counter something that real_ate said: "people use Slack threads". This is just categorically not true. 

    You might personally like and use Slack threads, that's fine, but in every Slack "server" I am a part of, people respond to comments without every finding the button to start a thread.

    I also agree with Mike's sentiments. There are a lot of people coming in here and saying "Please don't implement Flowdock's threads, they are terrible" but I have a very strong feeling that this is a vocal minority. If you surveyed everyone who has up-voted this feature I would imagine that a **vast** majority of people would say either "Please implement Flowdocks threads" or "I don't care how you do it just do threads". If anyone from Discord is listening please look past this vocal minority and consider what Mike is saying 👍

    -3
  • NewAlexandria

    The speed at which Discord could become worse is no excuse to do so.........

    -4
  • NewAlexandria

    of course it's not indicative of support — it's indicate of engagement / controversy.  That's what you use it to add to the primary value (votes)

     

    > Don't try to put your favorite on top by cherry-picking the numbers.

    Thanks, you put me in my place 👻

    -4

登入寫評論。