Can't unfollow atproto user from AP

[TomCasavant]

I accidentally followed a user with https://tomkahe.com/@ohgo (https://bsky.app/profile/mattsledge.xyz) I immediately unfollowed (which I think resulted in #1361). I've tried re-following, waiting 45 minutes and unfollowing and it still seems to show it's following that account on Bluesky https://bsky.app/profile/ohgo.tomkahe.com

[Fauli1221]

I managed to follow a unbridged profile and am also unable to unfollow it

[TomCasavant]

In my case it's definitely a bridged profile https://fed.brid.gy/bsky/mattsledge.xyz, but it does say the profile is only visible to logged in users

[Tamschi]

It definitely looks like #1361 to me, so @snarfed should hopefully be able to fix this manually since the record should still be on, well, record within Bridgy Fed's PDS.

To an extent, this is probably a design flaw in Bluesky though (which may also exist in some ActivityPub implementations, since the ActivityPub Primer currently has the same issue here: https://www.w3.org/wiki/index.php?title=ActivityPub/Primer/Follow_activity&oldid=116221#Multiple_Follow_activities).

To recover automatically from lossy transmission, the stored ID of unique relations must be the most recent one that would have created it, not the oldest or all ID(s). That way, it's always possible to create a state where the next delete/Undo properly removes the relationship, even if the sender loses all data aside from authorisation and the target object ID.

---

Edit: Filed:

• Brittle guidance regarding idempotent activities w3c/activitypub#485
• Clarify expected behaviour on receipt of additional records establishing an existing unique relation bluesky-social/atproto#3291

I don't have very high hopes since it probably involves infrastructure changes, but the latter would create a user-accessible workaround for this particular issue here if implemented in Bluesky-the-AppView. It's still fundamentally a Bridgy Fed bug, of course.

---

I managed to follow a unbridged profile and am also unable to unfollow it

That sounds like a separate problem. I assume you followed while the profile was bridged and then it was unbridged?
Bridgy Fed should break cross-network relations towards an account that becomes unbridged for some reason, since their author becomes unable to do so manually, but it sounds like it doesn't do that yet.