Mentions do not federate to non-Sharkey instances unless the capitlization is exactly correct
What happened?
User mentions (of the form @user or @user@host) don't federate to remote instances running software other than Sharkey when the capitalization differs from the handle's canonical form. The is resolved by the backend and appears correctly in the frontend and on other Sharkey instances. I've verified that the tag property is populated correctly, but the rendered note HTML contains the as-written (incorrect) capitalization instead of the canonical form referenced in the Mention object. This causes mapping failures on instances that use a case-sensitive search.
Despite the bug, notifications are still generated by Sharkey, Misskey, and Akkoma. On Akkoma, the impact appears limited to broken rendering - the handle appears as plain text and is not highlighted as a mention. On Mastodon, the mention is likely to be stripped since it won't resolve to any part of the text. (this behavior may have changed since I last used Mastodon). Upstream Misskey will "understand" the mention, but won't display it anywhere in the UI.
What did you expect to happen?
Mentions should be normalized to the correct capitalization before federating, or even before creating the note.
Version
2025.2.0-dev, also confirmed on 2024.11.2
Instance
enby.life, also confirmed on transfem.social
What type of issue is this?
server-side
How do you deploy Sharkey on your server? (Server-side issues only)
Build from source
What operating system are you using? (Server-side issues only)
Ubuntu Server 24.04
Contribution Guidelines
By submitting this issue, you agree to follow our Contribution Guidelines
- I agree to follow this project's Contribution Guidelines
- I have searched the issue tracker for similar issues, and this is not a duplicate.