Account Migration
- Allow taking your data archive and putting it somewhere else
- Doesn't allow all Zot 6 features such as connecting from another instance if your current one is down
- Will probably won't work for Mastodon followers
How it works:
- All actors (accounts, groups,…) have a generated uuid, which is transmitted over AP
- Old account tells (through an
update
activity) it's ID changed, and does this thing Mastodon uses to say the user has gone away to the new identity - Other Mobilizon instances update the ID
- User exports data from old instance (including private key)
- User imports data inside new instance
- A background task sends update activities for all content with the new id. Mastodon users will only get those if they subscribe again to the user (with it's new id)
- Remote instances accept it since the UUID and signature key is the same. Mastodon accounts should see only new content
Ways to improve:
- Send deletes for every content the old account had (after the user ID has been updated), but with the old user ID, so that mastodon users only have the new content