Ryan Barrett

One note here: if the pinned post isn't bridged yet, we'll need to bridge it first before we include it as pinned in the profile.

I'm actually thinking of inlining the full pinned post into the `featured` collection in AP actors, so ideally remote instances wouldn't even need to fetch it.

@lucidillusions hmm! The plan here right now is just to bridge fediverse pinned posts to/from Bluesky pinned posts automatically, no UI or triggering needed.

I've been trying to federate an actor with a pinned post to a Mastodon instance, by sending an `Update` for the actor, but no luck so far. Here's what I'm...

On the plus side, got it to work for fediverse => Bluesky! Example: https://indieweb.social/@snarfed => https://bsky.app/profile/snarfed.indieweb.social.ap.brid.gy . Will deploy to prod soon.

12 commits later, and I still haven't managed to convince Mastodon to see a pinned post. Interop, y'all, gotta love it. 🙄

So weird. Shipping this caused a massive flood of inbound requests from a bunch of Pleroma and Akkoma instances (maybe all the ones we federate with?), HTTP GETs for host-meta,...

Hmm! Yeah I guess that's the most obvious guess. Interesting that it was pretty much only those two though, not Mastodon, Misskey, Threads, Flipboard, etc. Also we only have ~60k...

This looks likely: https://akkoma.dev/AkkomaGang/akkoma/issues/831, _[bug] Spamming Fetch Requests #831_. Lots of `Could not decode featured collection at fetch https://mastodon.social/users/.../collections/featured` in the logs there.

I filed https://git.pleroma.social/pleroma/pleroma/-/issues/3379 to parallel that ^ Akkoma issue.