Ryan Barrett

Looked at how many of the big ones are over 90d old, specifically from before Oct 2024, the fractions range widely: | type | count | | ---- | -----...

So we have to keep the logic for checking `deleted` in various places [because we can't delete synchronously](https://github.com/snarfed/bridgy-fed/issues/1703#issuecomment-2605884155), but still, I think this is now done at least in spirit.

It's a good idea! We actually already do this, at least the quote post version, @Daft-Freak generously implemented it a couple months ago in #895, for https://github.com/snarfed/bridgy-fed/issues/1597#issuecomment-2521088052 . Feel free...

Tentatively closing. Feel free to reopen!

Hmm! I guess we could allowlist formats, but we could also just catch this exception? Might be easier and more forward compatible and also handle other errors we haven't thought...

Hey, good question! The Python library can, you can pass `Nostr.query` an arbitrary NIP-01 filter - https://granary.readthedocs.io/en/latest/source/granary.html#granary.nostr.Nostr.query - but the REST API can't. That could be a good addition! I'm...

Interesting. @aaronpk when wm.io does find mf2, does it only look for the target URL in the mf2 property values? This source doc has `h-entry`, but no explicit mf2 properties,...

Huh, surprising! Thanks for reporting. We've definitely had fediverse => Bluesky mentions working in general, so I'm not sure what happened here. I can look at some point.

Not sure what happened here, but I tried a fedi => Bluesky post with multiple mentions just now, https://indieweb.social/@snarfed/113612141635201822 => https://bsky.app/profile/fedi.test.snarfed.org/post/3lcpxopdymld2 , and the mentions bridged fine, so I suspect...

Yes! Great idea. I like it. One drawback is that it makes it more complicated to determine a Bluesky account's fediverse handle. Not too bad though, still reasonable. (Another drawback...