Summary
The mobile app reads kind-0 profiles for rendering (avatars, mention pickers) but provides no way to set or edit your own display name — Settings offers only a status field. Any identity created on mobile (invite join, buzz:// payload) is permanently unnamed and appears as a raw hex prefix (e1e0d007…) in the @-mention picker and member lists, for everyone in the community.
Impact
Reproduction
- Join a community on iOS via an invite (fresh identity generated on device).
- Open the @-mention picker in any channel → your identity renders as a hex prefix.
- Look for any name/profile editor in Settings → only "status" exists.
Suggestion
A display-name field in mobile onboarding (at join time) plus an editor in Settings that publishes the kind-0. Even a name-only editor (no avatar) would remove the hex-identity problem for mobile-first rollouts.
Summary
The mobile app reads kind-0 profiles for rendering (avatars, mention pickers) but provides no way to set or edit your own display name — Settings offers only a status field. Any identity created on mobile (invite join,
buzz://payload) is permanently unnamed and appears as a raw hex prefix (e1e0d007…) in the @-mention picker and member lists, for everyone in the community.Impact
Reproduction
Suggestion
A display-name field in mobile onboarding (at join time) plus an editor in Settings that publishes the kind-0. Even a name-only editor (no avatar) would remove the hex-identity problem for mobile-first rollouts.