AT —> AP: Bridged replies to bridged posts are not retrieved

[FurblandChannel]

To replicate:

1. Make a post on Bluesky from an account bridged to Fedi.
2. Reply to that post on Bluesky from a different, also bridged account.
   The expected behavior (the reply is fetched automatically) does not occur, even on instances where a user is following both bridged accounts. Instead, the reply is not fetched and must be retrieved manually.

[snarfed]

Right! This is expected right now. We only deliver replies to the upstream authors in the thread (background in #1218, #1608), not to all followers. AS2 audience targeting is notoriously complicated and under-implemented/ignored in the fediverse, but afaik this is the behavior it defines.

I don't actually know how much or which fediverse software currently delivers replies to all followers. Do you? One complicating factor is that shared inboxes mean AP delivery can effectively be global within each instance, so if you see a reply, that may only mean it was delivered to someone on your instance (who eg may have been earlier in the thread), not to you specifically.

[FurblandChannel]

As mentioned earlier, implementing Mastodon-style reply fetching for these replies might be beneficial as this would solve this issue (at least on some platforms)On Jan 6, 2026, at 8:27 AM, Ryan Barrett ***@***.***> wrote:snarfed left a comment (snarfed/bridgy-fed#2278) Right! This is expected right now. We only deliver replies to the upstream authors in the thread (background in #1218, #1608), not to all followers. AS2 audience targeting is notoriously complicated and under-implemented/ignored in the fediverse, but afaik this is the behavior it defines. I don't actually know how much or which fediverse software currently delivers replies to all followers. Do you? One complicating factor is that shared inboxes mean AP delivery can effectively be global within each instance, so if you see a reply, that may only mean it was delivered to someone on your instance (who eg may have been earlier in the thread), not to you specifically. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[snarfed]

Sure! Happy to merge this into #1739 if that works for you.

[FurblandChannel]

Sounds great! Thanks :)On Jan 6, 2026, at 9:24 PM, Ryan Barrett ***@***.***> wrote:snarfed left a comment (snarfed/bridgy-fed#2278) Sure! Happy to merge this into #1956 if that works for you. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>