Repository navigation
Group chat: simplify bot display name to bot name + username #526
Description
Summary
In group chat, the bot display name currently looks like:
Reviewer · FlyBot 682b8a43 (flybot682b8a43)
This is hard to read and does not help users identify who they are talking to. Please simplify it to bot name + username.
Steps to reproduce
- Join / open a group chat that includes a FlyBot participant.
- Look at the bot’s display name in the member list or message header.
Expected
A short, human-readable label, e.g.:
Reviewer · @username- or
Reviewer (username)
i.e. bot name + username only — no opaque hash / duplicate slug.
Actual
Something like: Reviewer · FlyBot 682b8a43 (flybot682b8a43)
- Includes a truncated / hashed id (
682b8a43) - Repeats a slug form (
flybot682b8a43) next to the same information - Hard for end users to parse at a glance
Ask
- Change group-chat bot display names to bot name + username.
- Drop the internal id / duplicate machine-style slug from the default UI label (keep full ids in tooltips / debug views if needed).
Activity
Birfy commentedon Oct 20, 2026
Triage (Birfy, 2026-10-20 17:59 Asia/Shanghai): bug, same family as #498 (PR #502, one person-first formatter for a friend's Bot:
Chief (SelfB1233)). Proposed fix: group/face-room labels use that same formatter, i.e.Reviewer (flybot682b8a43)(Bot name + owner's username); drop an auto-generatedFlyBot <hash>display name when it is only derived from the id; full ids stay in the tooltip. Build after #502 lands. Waiting for the owner to confirm (needs-human).Birfy commentedon Oct 20, 2026
Owner decision (Danyang Chen, 2026-10-20 18:13 Asia/Shanghai): option (a). Reuse the #498 / PR #502 name format:
Reviewer (flybot682b8a43)= Bot name + owner username. Drop the autoFlyBot <hash>name; the full id stays in the tooltip. Work starts after #502 merges.Birfy commentedon Oct 20, 2026
Claimed by Birfy (maintenance, 2026-10-20 20:01 Asia/Shanghai). Branch
fix/526-group-bot-labelon Birfy/FlyBot, stacked on #502's branch (same person-first formatter, per the owner decision); the PR will say so and land after #502.Birfy commentedon Oct 20, 2026
PR #541 (Birfy, 2026-10-20 20:18 Asia/Shanghai): built on #502's branch, per the owner decision (option a). Merge it after #502.
Minor UI details I decided:
FlyBotfollowed by a hex id with at least one digit (FlyBot 682b8a43).FlyBot,FlyBot2(the Social startup: fresh install fails on a taken handle (default displayName 'FlyBot'), and my own handle is never shown #136 retry name) andFlyBot Teamare real names and stay. The made-up name is replaced by the owner's username from the home handle (@….flybot682b8a43.home→flybot682b8a43). If no handle is known, the made-up name stays, since it is better than no name.flybot682b8a43), so the person and their Bots read the same. This applies to the join, leave and room-lead lines (Reviewer (flybot682b8a43) joined,flybot682b8a43 left the room) and to a line that person typed.· <owner>loses that tail only when it is the Bot's own owner (Bot Social's member label). A·that is part of a Bot's real name is kept (Ops · Night (Bob)).Name a group or face-room Bot by its name and owner username (ThinkFl…