Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix custom emoji compatibility in Misskey's display name #15478

Conversation

noellabo
Copy link
Contributor

@noellabo noellabo commented Jan 3, 2021

In Misskey, you can use custom emoji in display_name without whitespace, but in Mastodon it will be displayed as a shortcode.

To remedy this incompatibility, insert zero width space before and after the shortcode. Only the shortcodes included in the emoji tag are targeted.

(There are no changes to Mastodon's rules)

fix_emoji_displayname

@noellabo noellabo force-pushed the fix-custom-emoji-compativility-in-misskey-s-displayname branch from 95c083d to d519c49 Compare January 3, 2021 20:37
@ClearlyClaire
Copy link
Contributor

The need for a space (zero-width or otherwise) between two custom emoji is to accommodate things like IPv6 addresses in messages, so I'm a bit uneasy with this change for this reason. On the other hand, the fact that this only applies to shortcodes that are present in the remote server's payload should make it an exceedingly rare issue though. That being said, if we do that for display names and not for toot content, we introduce a weird inconsistency.

@noellabo
Copy link
Contributor Author

noellabo commented Jan 8, 2021

Ah, IPv6!

You'll find it strange that it doesn't convert Toot content, but Misskey itself inserts whitespace, so we didn't have to deal with it here.

If we limit ourselves to display names, we don't need to be able to parse IPv6 addresses correctly, and it seems to me that we can ignore the rare cases of incorrect conversion.

Base automatically changed from master to main January 20, 2021 10:31
@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/wontfix This will not be worked on label Jun 2, 2021
@stale stale bot closed this Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/wontfix This will not be worked on
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants