Migration effects where followers get stuck in pending #443
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#443
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
OTP
Extra details
No response
Version
No response
PostgreSQL version
No response
What were you trying to do?
I migrated from a self-hosted Mastodon to a fresh install of Akkoma on January 11.
What did you expect to happen?
I expected a bit of trouble, but did not expect to lose most of my followers.
I expected most of my followers to re-follow the new account.
What actually happened?
Here are some of the issues I've seen with followers.
At time of migration I had 3,600 followers. About 1,000 followers "carried across" during migration (I thought) and were listed as followers. 117 followers stayed with the old account. About 2,500 followers appear to be in limbo.
For the following description it's important to understand I have never had approval request of followers and do not plan to. And it took me about a week to figure out these circumstances. So there was plenty of time for the follows to start working.
As it turns out:
So a lot of different stuff going on. My theory is that the large number of followers automatically requesting a follow caused queuing and cancellations of follow requests. The concern is that there is no way of knowing if the refollows will try automatically again (they haven't in 11 days).
Also many people are now seeing a pending request instead of a follow button when visiting my profile. They assume I'm not approving a follow rather than realising they need to retry the follow.
Logs
Severity
I can manage
Have you searched for this issue?