Unliking on Bluesky not mirrored to Mastodon

[sayunuh]

In a mutually bridged state between ActivityPub <-> Bluesky (both accounts mine), after liking a bridged Mastodon post on Bluesky, unliking it doesn’t seem to mirror to the Mastodon server properly. The “favorited” notification doesn’t disappear, and the post’s favorites count doesn’t decrease. In contrast, undoing a repost does seem to mirror properly (after some expected delay). On https://fed.brid.gy/ap/ I can observe unliking (likes disappearing), but it’s not seen on the Mastodon server. Can it be fixed? I cannot confirm whether it’s my server’s fault or not.

[snarfed]

Hmm! Sorry for the trouble. Which post was this, and which account liked and unliked it?

[Tamschi]

That's probably #1361 if unliking was done shortly after liking the post.
Also related to bluesky-social/atproto#3291 since that would provide a workaround.

[sayunuh]

This is the Bluesky account:
https://bsky.app/profile/sayunu.bsky.social

And these are the posts:
https://mofu.kemo.no/@sayunu/113574781088219263
https://mofu.kemo.no/@sayunu/113559039920972955
https://mofu.kemo.no/@sayunu/113559901388518271

The operation was like this:

1. Sent a post on the Mastodon web UI
2. Saw it on the bsky.app web UI
3. Liked it
4. In less than ten seconds, received a notification regarding it on the Mastodon web UI; saw the favorites count increasing
5. Unliked it
6. Waited several minutes, reloaded the Mastodon web UI
7. The notification persisted; the favorites count was unchanged

[snarfed]

Finally looking at this, thanks for your patience.

The 2m delay for deletes and undos that we added in #1361 (comment) applies to unlikes, so if this is #1361, I'd be disappointed that that delay isn't preventing it. I'll look.

[snarfed]

Looking at Bridgy Fed's logs, we sent the Undo activity below for this like at 2024-12-24 09:14:36 UTC and got an HTTP 202 response:

POST https://mofu.kemo.no/users/sayunu/inbox

{
  "@context": ["https://www.w3.org/ns/activitystreams"],
  "type": "Undo",
  "id": "https://bsky.brid.gy/convert/ap/at://did:plc:fsbgmc2snml3wqdfxt2k5ofl/app.bsky.feed.like/3le27gpmr6p23#undo",
  "actor": "https://bsky.brid.gy/ap/did:plc:fsbgmc2snml3wqdfxt2k5ofl",
  "object": "https://bsky.brid.gy/convert/ap/at://did:plc:fsbgmc2snml3wqdfxt2k5ofl/app.bsky.feed.like/3le27gpmr6p23",
  "to": ["https://www.w3.org/ns/activitystreams#Public"],
  "cc": [
    "https://mofu.kemo.no/users/sayunu",
    "https://www.w3.org/ns/activitystreams#Public",
    "https://mofu.kemo.no/users/sayunu/followers"
  ]
}

Bluesky => fediverse unliking is working in general afaik, so I can't say why mofu.kemo.no didn't like this Undo specifically. Maybe ask that instance's admins to check their logs?

[snarfed]

Tentatively closing since it looks like Bridgy Fed did the right thing here. @sayunuh feel free to reopen or update if you learn any more from mofo.kemo.no's side!

[sayunuh]

OK, sorry for taking your time. I’m relieved to know that the issue isn’t affecting too many people.