Signal-desktop: React with arbitrary emoji.

[iago-lito]

• [x] I have searched open and closed issues for duplicates

I love the new "reaction" feature :) Thank you for this, I already use it all the time to just stick an emoji to the message rather than sending another message with just an emoji in it.

However, I've quickly found myself limited in the set of "reactions" offered. I understand that it is very basic like the one GitHub features:

On Gitlab and Mattermost, I think that any unicode emoji is accepted as a "reaction".
With Signal, I still need to fall back on answering a single-emoji-message when I want to react with :nauseated_face:, :1st_place_medal: or :ok_hand:.

Is it something wanted in Signal for the future if "reactions" turn out to work well? I personnaly would love this :)

Thank you for support, and thank you for Signal!

[fnetX]

I propose to keep the dialogue as simple as it is, but allow either for customization (personally I'd like to add that shrugging (:man_shrugging:) one) or take the keyboard's latest section in case it is accessible from Signal. It 's probably more than one row, but horizontal scrolling might be an option.

A 'more' dialogue will still be helpful if you need an uncommon one :-)

[iago-lito]

@fnetX Yeah, then why not going further with one simple dialogue like this, but featuring only the 7 most used custom ones. I might end up with something like | :tada: :heart: :hankey: :pray: :1st_place_medal: :question: :ok_hand: | 0:)

[alex]

This feature is now supported on iOS and Android, and Signal for Desktop can render them, it just can't send them.

[kenpowers-signal]

@alex This will be in our next public beta. For the time being you can enable sending any emoji on Desktop by entering the following into the dev console (cmd+opt+i on mac, ctrl+shift+i on Linux/Windows):

window.REACT_ANY_EMOJI = true

[yurrriq]

Given the : functionality in messages, it would be great to able to type e.g. +:exploding_head: to react with :exploding_head:.

[scottnonnenberg-signal]

I'm going to close this, since we've release this to production.