Conversation
Notices
-
Embed this notice
Following works fine between the Pleroma server and the Rebased server, in other words I have no leads on why we sometimes can't follow remote people.
-
Embed this notice
@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.
-
Embed this notice
@sun oh so i'm not insane, my follows really are getting thrown into the abyss
I think it happens more often (for me) when i try to follow from the usercard popup thing as opposed to the page itself
-
Embed this notice
@sun you imported users to the new database, what about relationships?
-
Embed this notice
@graf no, everyone was required to either migrate or just manually refollow everyone.
several remote follows don't work. I can't follow Alex Gleason for example.
-
Embed this notice
@denza252 in some cases it just immediately flips back to "follow" and sometimes it says it's requested and never finishes.
-
Embed this notice
@denza252 @sun With accela.i2p I had to return 400 for the /users/x/following and /users/x/followers endpoints so that other instances won't get stuck in loop re-requesting them. Still gets stuck at "request sent", but less so than before.
-
Embed this notice
@sun Alex might have a bug in his server. we can't follow several users on his instance. most notably @caekislove but there was some others i can't remember