💡 Summary
A supported feature of activity pub is to not tie the host part of an acct, for example @example.com to the instance host, for example social.example.com. Misskey only stores the username and the instance host url for all remote users, and does not report the correct user acct.
The solution is to store the subject returned from a remote users webfinger lookup in the database entry for that user. Then use this subject in the ui if set, and fallback to @username@host if not.
🥰 Expected Behavior
Given an activity pub instance at social.example.com with user @user@example.com, misskey should report to the ui @user@example.com.
🤬 Actual Behavior
Given an activity pub instance at social.example.com with user @user@example.com, misskey reports to the ui @user@social.example.com.
📝 Steps to Reproduce
- Lookup any remote user on any instance with the instance/federation host's different, see that the user is reported with the wrong acct
💻 Frontend Environment
Tested on both:
* Model and OS of the device(s): Linux
* Browser: Firefox
* Server URL: https://misskey.io/
* Misskey: 2025.12.2
* Model and OS of the device(s): Linux
* Browser: Firefox
* Server URL: https://social.freya.cat/
* Misskey: 2026.3.0 (with changes from #17222)
🛰 Backend Environment (for server admin)
For https://social.freya.cat:
* Installation Method or Hosting Service: Selfhost
* Misskey: 2026.3.0 (with changes from #17222)
* Node: 22.21.1
* PostgreSQL: 17.9
* Redis: 7.4.8
* OS and Architecture: Linux amd64
Do you want to address this bug yourself?
💡 Summary
A supported feature of activity pub is to not tie the host part of an acct, for example @example.com to the instance host, for example social.example.com. Misskey only stores the username and the instance host url for all remote users, and does not report the correct user acct.
The solution is to store the subject returned from a remote users webfinger lookup in the database entry for that user. Then use this subject in the ui if set, and fallback to @username@host if not.
🥰 Expected Behavior
Given an activity pub instance at social.example.com with user @user@example.com, misskey should report to the ui @user@example.com.
🤬 Actual Behavior
Given an activity pub instance at social.example.com with user @user@example.com, misskey reports to the ui @user@social.example.com.
📝 Steps to Reproduce
💻 Frontend Environment
🛰 Backend Environment (for server admin)
Do you want to address this bug yourself?