Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://fed.brid.gy/r/https://snarfed.org/2025-07-19_randahl-fink-update-i-talked-to-harriett-mastodon">Ryan Barrett (snarfed.org@fed.brid.gy)'s status on Sunday, 20-Jul-2025 07:15:59 JST</a><a href="https://fed.brid.gy/r/https://snarfed.org/" title="snarfed.org@fed.brid.gy"><img src="https://gnusocial.jp/avatar/121991-48-20231020213632.webp" width="48" height="48" alt="Ryan Barrett" style="position: absolute; left: 0; top: 0;">Ryan Barrett</a><div><a href="https://mastodon.social/@randahl/114875127725908882" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/281584" title="harriettmb@beige.party">HarriettMB</a></li></ul></div></section><article><p>This was clearly an awful situation for everyone involved. Sorry <a href="https://mastodon.social/@randahl">@randahl</a> and <a href="https://beige.party/@HarriettMB">@HarriettMB</a>! Neither of you deserved this.
</p><p>I investigated and confirmed that this was due to a bug in the bridge. It was always designed to avoid link previews for @-mentions, and usually did, but in a few rare cases like this one, it didn’t. That bug was fixed back in March, just days after the post in question here. Tough timing. Details: <a href="https://github.com/snarfed/bridgy-fed/issues/1987">https://github.com/snarfed/bridgy-fed/issues/1987</a></p>
<p>Apologies again for the bug and misunderstanding here.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/5375810#notice-10552186">In conversation</a><time datetime="2025-07-20T07:15:59+09:00" title="Sunday, 20-Jul-2025 07:15:59 JST">about a year ago</time> <span>from <span><a href="https://fed.brid.gy/r/https://snarfed.org/2025-07-19_randahl-fink-update-i-talked-to-harriett-mastodon" rel="external" title="Sent from fed.brid.gy via ActivityPub">fed.brid.gy</a></span></span><a href="https://fed.brid.gy/r/https://snarfed.org/2025-07-19_randahl-fink-update-i-talked-to-harriett-mastodon">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: opengraph.githubassets.com</div><h5><a href="https://github.com/snarfed/bridgy-fed/issues/1987">AP =&gt; AT: Do not link to non-bridged user profile(s) · Issue #1987 · snarfed/bridgy-fed</a></h5><div></div></header><div>When a bridged ActivityPub user creates a post, with a mentioned to an account that is not bridged, do not bridge the post. Rationale Some account holders do not want their presence to be propagate...</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Ryan Barrett (snarfed.org@fed.brid.gy)'s status on Sunday, 20-Jul-2025 07:15:59 JSTRyan Barrett
in reply to
- Randahl Fink
- HarriettMB
This was clearly an awful situation for everyone involved. Sorry @randahl and @HarriettMB! Neither of you deserved this.
I investigated and confirmed that this was due to a bug in the bridge. It was always designed to avoid link previews for @-mentions, and usually did, but in a few rare cases like this one, it didn’t. That bug was fixed back in March, just days after the post in question here. Tough timing. Details: https://github.com/snarfed/bridgy-fed/issues/1987

Apologies again for the bug and misunderstanding here.
In conversationabout a year ago from fed.brid.gypermalink
Attachments
1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
  AP => AT: Do not link to non-bridged user profile(s) · Issue #1987 · snarfed/bridgy-fed
  When a bridged ActivityPub user creates a post, with a mentioned to an account that is not bridged, do not bridge the post. Rationale Some account holders do not want their presence to be propagate...

Public

Embed Notice

HTML Code

Corresponding Notice