Summary
When sending a message if it contains a an emoji that has been inserted via the emoji picker or the emoji autocomplete, it would not get converted to a proper unicode emoji when sending the message. While not being a very big issue, it can be confusing for bots, as there is no way to tell if the user typed the shortcode intentionally while not meaning to send an emoji.Steps to reproduce
- Open a fluxer client ( Reproducable both on desktop client as well as the official https://web.fluxer.app/ client )
- Open developer tools to inspect the network requests
- Send a message with an emoji via the emoji selector or by auto completing it. ( Not copy and pasting a unicode emoji directly )
- Check the API call that sent the message to the server and look at the payload/body

6 comments
Comment by -Tempestas Avantgarde-
560461035-bbaa2cfc-9fb7-48ca-8502-e22588ef4f5e.png
722×639 | 65 kB Link to 560461035-bbaa2cfc-9fb7-48ca-8502-e22588ef4f5e.png
560461230-8a4e175c-8084-44eb-8c55-bb3d24b539a3.png
722×639 | 65 kB Link to 560461230-8a4e175c-8084-44eb-8c55-bb3d24b539a3.png
Comment by @roufpup
This is not about what the client shows in debug mode but what it sends to the api. Try the reproduction steps i gave.Okay this is really weird i asked someone else to test it too and they also had the emoji be sentComment by -Tempestas Avantgarde-
Comment by @roufpup
Comment by Emma~xoxo
Comment by @roufpup