The migration of the Bot from botsin.space to mastodon.scot has gone without mishap, confirming the Fediverse portability principle.
- After doing a Create Account and email confirmation on the target service, I went to the Development page from the Preferences, and added a new application with "write" entitlement, and then grabbed Your access token as the secret file for Python to access.
- The host name and the secret file provide the new api_base_url and access_token values for the Python Mastodon function. First messages can then be sent on the new account.
- The new account's Account Settings are then adjusted to specify the old account as an alias under "Moving from a different account". Nothing actually happens at this point.
- Then, in mirror activity on the old account's Account Settings, specifying the new account under "Moving to a different account" (in form acme@new.service) quickly triggers a mass of pings as each follower is set up on the new account.
