Unable to transfer all followers back to Mastodon instance from Iceshrimp #521

Open
opened 2024-02-20 13:43:33 +01:00 by revengeday · 2 comments

A user from our Mastodon instance moved to our Iceshrimp instance and now wishes to return to our Mastodon instance. While the migration from Mastodon to Iceshrimp went smoothly, the user has encountered difficulties in transferring all their data back. Many followers are missing upon returning to Mastodon.

Unfortunately, we have been unable to find a way for the user to retrieve their followers back. These followers are currently stuck on the old profile on our Iceshrimp instance. We attempted to have the user migrate again from Mastodon to Iceshrimp and back, but this did not resolve the issue as their user account indicates they have already migrated.

Is there a workaround to revoke the migration status in Iceshrimp so that the user can attempt the transfer again?

A user from our Mastodon instance moved to our Iceshrimp instance and now wishes to return to our Mastodon instance. While the migration from Mastodon to Iceshrimp went smoothly, the user has encountered difficulties in transferring all their data back. Many followers are missing upon returning to Mastodon. Unfortunately, we have been unable to find a way for the user to retrieve their followers back. These followers are currently stuck on the old profile on our Iceshrimp instance. We attempted to have the user migrate again from Mastodon to Iceshrimp and back, but this did not resolve the issue as their user account indicates they have already migrated. Is there a workaround to revoke the migration status in Iceshrimp so that the user can attempt the transfer again?
Owner

Fedi migrations are special, you aren't really transferring the followers, you're telling all the instances with following users "hey, i've moved!". You can't force them to acknowledge this. I can't say for sure what went wrong during the migration. If you want to try again, the migration-related properties on a user account are alsoKnownAs and movedToUri, though I cannot guarantee you won't break anything by retrying this step. Maybe @erincandescent knows more about the technical implications of doing this?

Fedi migrations are special, you aren't really transferring the followers, you're telling all the instances with following users "hey, i've moved!". You can't force them to acknowledge this. I can't say for sure what went wrong during the migration. If you want to try again, the migration-related properties on a user account are `alsoKnownAs` and `movedToUri`, though I cannot guarantee you won't break anything by retrying this step. Maybe @erincandescent knows more about the technical implications of doing this?
Author

The Fediverse and its special problems. 😄 I tried with a test account to move from our Mastodon instance to our Iceshrimp instance and then back to Mastodon. Now both accounts are stuck in limbo.

https://corteximplant.com/@test19022024
https://nightcity.bar/@test19022024

Would it be possible to submit the following as a feature request:
When moving from one Mastodon instance to another and then back, it seems that at least with Mastodon, a trigger is set to reactivate the old account. It seems that with Misskey forks, it doesn't (yet) work.

The Fediverse and its special problems. 😄 I tried with a test account to move from our Mastodon instance to our Iceshrimp instance and then back to Mastodon. Now both accounts are stuck in limbo. https://corteximplant.com/@test19022024 https://nightcity.bar/@test19022024 Would it be possible to submit the following as a feature request: When moving from one Mastodon instance to another and then back, it seems that at least with Mastodon, a trigger is set to reactivate the old account. It seems that with Misskey forks, it doesn't (yet) work.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: iceshrimp/iceshrimp#521
No description provided.