Well Discourse doesn’t have that, and the only way to view reactions in bulk easily is to hover over the reaction to see who reacted, or by holding the reaction which can feel awkward for holding a small button. This can start to feel time-consuming and unorganized when doing this with many. This is how discourse’s menu looks.
On discord, you can easily open the contextual menu to see who reacted with a right click and a left click. The menu is more organized than discourse’s implementation of reactions in chat. This menu is much easier to read and control than when you use discourse to look at the reactions in chat.
My idea was to add this much better implementation of looking at reactions over to Discourse, in the chat. This might also be able to be implemented elsewhere, like forums with Discourse Reactions installed. On topic posts with discourse reactions, this looks a little better, but my idea was to add a smiley button on the side to see a list of who reacted with what like discords. This is discourse’s reactions menu in long form posts, which is better than the implementation in chat already:
On chat if more than 5 people react / give a thumbs up to a message than it says the first 5 names “and N others reacted with ”.
Our support team wants to get in touch with everyone who reacted to this message but there does not seem to be any way to get a list of all the people who responded.
Is there any way to get the full list of people who react to a message in chat?
Thanks @NateDhaliwal . I tried that out but when I go to /chat/api/channels/:id/messages.json it only shows me the same 5 users which are showing in the UI with no way to get the others (see screenshot below).
Pinging @j.jaffeux from that API thread in case he knows how to do it. Very frustrating to not be able to see who responded / reacted to the message as we have no way of contacting the people who expressed interest / requested to be contacted.
Hi Earnie! If you have the data explorer plugin on your site, you can probably create a query there to get the information you need. But you’re right that it seems to be an oversight that this information isn’t just available in the interface, which we already have in posts.