Separate visible text from the account it identifies
Copying '@alex' preserves characters, not proof that the intended Alex owns that name on another network. The person may use a longer handle, a domain-based identity, or no account there at all. Before cross-posting a mention, confirm the destination profile using a reliable reference such as the person's own website or a direct confirmation. Similar names and avatars alone can be misleading.
Bluesky makes the distinction explicit in its documentation. Mentions are rich-text annotations that refer to an account DID, while the visible handle sits in the post text. Links use a different annotation. A tool must construct the relevant destination representation, not merely copy an at-sign. This is a platform example, not a promise that every publishing tool resolves or maps identities automatically.
Keep a small attribution map for recurring collaborators
For people you mention frequently, maintain their approved display name, destination profile URLs, and verification date. Store the person separately from each account. A handle can change while the underlying identity stays the same, and a familiar username can mean something different elsewhere. Review the map before a collaboration launch instead of discovering a wrong tag after several copies have gone public.
The example below uses fictional people and reserved example domains. It demonstrates the decision rather than claiming these are real social accounts. A blank destination is a legitimate result: it means you need another attribution method, not that you should guess. If the creator prefers not to be tagged on a particular platform, respect that choice even when an account exists.
| Person | Destination evidence | Publishing decision |
|---|---|---|
| Alex, tutorial guest | Verified destination profile supplied by Alex | Use the supported native mention |
| Sam, photographer | Website at sam.example; no verified destination account | Use credited name and appropriate website link |
| A name matching several profiles | Identity unresolved | Ask before tagging; do not guess |
Check the actual mention after publication
In the composer, verify whether the selected mention is an account reference or just visible text. After publishing, inspect the destination copy and follow the tag where possible. The expected outcome is the correct profile, not merely blue text. If the tool transforms or splits the post, inspect the version containing the attribution rather than assuming the source selection survived every transformation.
If a mention remains plain text, first check whether the destination supports that tagging operation through the chosen route. Then check whether the account was actually resolved and whether the publisher exposed the required control. Plain text can be an intentional fallback rather than a transport failure. Do not remove accurate attribution just to make the post look cleaner, and do not turn a person's name into an unrelated clickable tag.
Correct wrong tags without multiplying the mistake
Record which copies contain the incorrect mention and use the supported correction method for each destination. Editing the original does not prove that every distributed copy updates. If a replacement is necessary, check existing posts and pending automation before resending. Explain a consequential attribution correction plainly rather than letting the wrong account continue to receive attention or notifications.
For a support report, include the intended profile, visible text, destination URL, publishing route, and what clicking the tag actually does. Keep private contact information out of the report. When using Ferryman, verify the destination behavior of your specific workflow rather than assuming an origin mention maps everywhere. Accurate plain-text credit with a verified link is preferable to an impressive-looking tag that identifies the wrong person.
Sources & further reading
Written by Ferryman. Sources checked Oct 16, 2026. Platform rules can change; consult the linked documentation for current requirements.