Edit history

Fediverse embeds show linked instance domain instead of the author’s home server in user handle when shared from *key or Pleroma has not been edited, so there are no earlier versions.

Current version | Original by Melon
Show

Fediverse embeds show linked instance domain instead of the author’s home server in user handle when shared from *key or Pleroma

Reproduction steps

  1. Post a Mastodon post using a link from a Misskey/Sharkey/Pleroma instance (example: https://ap.fruity.website/notes/atbnlo8oz21s1zzg)
  2. Check the title of the embed
  3. Title will show the user but at your *key instance's domain
I'm not sure if this happens on other non-Mastodon Fediverse software. A Pleroma server running version 2.10.2 seemed to also have this issue, while a different Pleroma server running version 2.5.5 fell back to using its regular OpenGraph embed, so it displayed correctly.

Expected behaviour

The embed would use the authors handle in the title/label, with the proper domain. Example: Fluxer (@fluxer@fluxer.com)

Actual behaviour

The embed title uses the domain of the link, rather than the post author's home server domain. Example: Fluxer (@fluxer@ap.fruity.website)

Build information

Canary Desktop 2026.1116.70910, Web 2026.1117.140332, Linux 7.2.12+deb13-amd64 (x64), Electron 44.10.0, Chrome 152.0.7977.169, Node 24.22.1, Locale en-US

Platform

API, Self-hosting

Evidence

In the example you can see four Fediverse posts. When the remote post is linked through my Sharkey instance, Fluxer uses my instance’s domain in the author handle instead of the author’s home server. The first two are the same post, but one is linked directly from Fluxer's GoToSocial instance, whereas the second is a federated version of that post from my Sharkey instance. In the embed for my instance you can see that the label is listing the author as @fluxer@ap.fruity.website instead of @fluxer@fluxer.com. Below those are two posts from Sharkey instances, one local to my instance and one from a remote server, splatsville.social. Both of these appear fine since they appear to be using their OpenGraph embeds, which have the correct author handle. example_image3.png Speculation as someone who doesn't know Rust: The resolve_actor_author function in formatter.rs seems to get the domain from context.server_domain, which it gets from build_context() in mod.rs. build_context appears to try checking /api/v2/instance for the instance via fetch_instance_info() in fetcher.rs, or falls back to a cleaned URL it makes. Either way, this looks like it's using the linked URL instead of the actual host of the ActivityPub actor.