You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Toot on a Mastodon instance with a unicode hashtag like #ć.
Get the post at an Akkoma instance.
Look at the hashtag #ć on that instance.
Expected behaviour
The post appears there
Actual behaviour
The post is not there, but it is under #c
Detailed description
Hashtags get "normalized" to ASCII(?) in some instances. Then during federation only the "normalized" variant gets sent, instead of the actual hashtag. See https://akkoma.dev/AkkomaGang/akkoma/issues/568 for some more technical details.
It would be nice to not perform this "normalization" at all, since 'ć' and 'c' are barely connected distinct letters, but failing that at least federating the actual hashtag would be preferable.
Specifications
I was on the Akkoma end of this interaction, but there were a couple Mastodon instances involved, and all had the problem.
The text was updated successfully, but these errors were encountered:
Steps to reproduce the problem
Expected behaviour
The post appears there
Actual behaviour
The post is not there, but it is under #c
Detailed description
Hashtags get "normalized" to ASCII(?) in some instances. Then during federation only the "normalized" variant gets sent, instead of the actual hashtag. See https://akkoma.dev/AkkomaGang/akkoma/issues/568 for some more technical details.
It would be nice to not perform this "normalization" at all, since 'ć' and 'c' are barely connected distinct letters, but failing that at least federating the actual hashtag would be preferable.
Specifications
I was on the Akkoma end of this interaction, but there were a couple Mastodon instances involved, and all had the problem.
The text was updated successfully, but these errors were encountered: