Custom emojis with non-ASCII names don’t render

[JadedCtrl]

💡 Summary

Custom emojis with non-ASCII names don’t seem to render on Misskey servers.

🥰 Expected Behavior

Custom emojis with non-ASCII names should render normally, like other custom emojis.

I’ve made an example post on a Pleroma server, with the emoji names :taneŝima_ĝojas:, :मार्जारः:, :鹅:, :taneŝima_malsanas:, :แมว:, and :लक्षणा:.

Here’s what it looks like on the Pleroma server:

🤬 Actual Behavior

On Misskey servers, emojis with non-ASCII names don’t display at all, and you only see the emoji names.

The above post looks like this on misskey.io:

📝 Steps to Reproduce

1. Try to view a post with non-ASCII emoji names, like that pinned to my profile, @JadedCtrl:jam.xwx.moe.

💻 Frontend Environment

* Model and OS of the device(s): Arch GNU/Linux
* Browser: Firefox
* Server URL: https://misskey.io
* Misskey: v2024.2.0-io.1

🛰 Backend Environment (for server admin)

* Installation Method or Hosting Service:
* Misskey:
* Node:
* PostgreSQL:
* Redis:
* OS and Architecture:

Do you want to address this bug yourself?

• Yes, I will patch the bug myself and send a pull request

[saschanaz]

(This happens on Mastodon too, and there probably should be better federation with actual indices as Twitter API does instead of depending on parser rules of each receivers)