Once entities expose an origin home domain, users need to see at a glance which people/messages come from another server.
What to do
- Show the home domain (e.g.
@b.example) next to remote usernames in the member list, message author line, and member popout/profile.
- Add a subtle 'federated' badge/icon on remote avatars.
- Make the remote profile popout read-only where local-only actions don't apply (e.g. role assignment that the local server can't perform on a remote user).
Acceptance
- A remote user is visually distinguishable from a local one in member list, chat, and profile views.
- Local users render exactly as before (no badge, no domain suffix).
Depends on
- Qualified-ID/
origin modelling.
Client touch points
lib/features/member/views/accord_member_list.dart, accord_member_avatar.dart, accord_member_popout.dart, lib/features/member/utils/member_display.dart.
Server reference — accordserver branch claude/federated-servers-xlydlj.
Once entities expose an
originhome domain, users need to see at a glance which people/messages come from another server.What to do
@b.example) next to remote usernames in the member list, message author line, and member popout/profile.Acceptance
Depends on
originmodelling.Client touch points
lib/features/member/views/accord_member_list.dart,accord_member_avatar.dart,accord_member_popout.dart,lib/features/member/utils/member_display.dart.Server reference — accordserver branch
claude/federated-servers-xlydlj.