@denza252 @sun It's using the exact same API call. There's a long-standing issue where the follow (or unfollow) could stuck in ghost state where the Accept/Undo activitity exists in DB but there's no corresponding entry in following_relationships, plus a possible race condition when the unfollow is sent before the accept arrives (very prominent on Tor/I2P instances), but I wouldn't know if that's related to whatever is happening here.