Dear @SlackHQ, when I react to a comment with :fistbump:, please do not display it as :facepunch:. Can you see the problem?
-
-
W odpowiedzi do @adamralph
Yep, that's a bit of a problem alright and definitely messes up what could have been a great fistbump moment. There's also the left and right facing fist emoji that illustrate a fistbump pretty nicely, worth a shot (also add in something suitably epic in between them).
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @SlackHQ
still a problem... happened again today
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @adamralph
Hi, Adam!
It might be worthwhile creating an emoji alias so that it appears as :fistbump: when used in the future:https://slack.com/help/articles/202931348-Use-emoji-and-emoticons#create-an-emoji-alias …1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @SlackHQ
Not sure I understand. :fistbump: is already an alias for :facepunch: (as far as I can tell). It seems that is exactly what leads to the problem. BTW, if I write :fistbump: in a message, it remains as :fistbump:. Only when used as a reaction does it get converted to :facepunch:
2 odpowiedzi 0 podanych dalej 0 polubionych
Ah apologies there! You are indeed correct. When you use an emoji alias *as a reaction* we map it onto its original name (in this case :facepunch:). In-line emoji doesn't get the same treatment and that difference is certainly something we're working on.
Wydaje się, że ładowanie zajmuje dużo czasu.
Twitter jest przeciążony lub wystąpił chwilowy problem. Spróbuj ponownie lub sprawdź status Twittera, aby uzyskać więcej informacji.