@shinmera@mastodon.tymoon.eu if you're looking for a solution that is doable today, then that would be setting up the new site, iterating over your old user database to set movedTo, iterating over the new user database to set alsoKnownAs, and then publishing a Move to every user's followers.

That'd preserve user accounts and migrate followers, but lose content.

@julian What about automated export and import of the posts? So that they at least exist in the new history, even if other federated servers will still point to the old domains?

@shinmera@mastodon.tymoon.eu oh sure I assume that would be taken care of if you're literally just changing domains, the underlying database is still the same.

This is assuming the software didn't hardcode the IDs with the old domain

@julian I know absolutely nothin' about mastodon internals

@shinmera@mastodon.tymoon.eu oh yes, I should also mention there is no user friendly tooling to do this.

@shinmera @julian there's no support for importing toots from other instances. Your export is only an archive.

@shinmera GoToSocial has a Mastodon migration tool, I see it’s archived though https://github.com/VyrCossont/slurp/

@django thanks. it's only archived cause it's now on codeberg (nice) https://codeberg.org/vyr/slurp

@shinmera oh I missed that, awesome!

@shinmera when my main acces domain moved from mastodon to social I just changed the settings and made everything redirect there. Probably only broke the I stances that can't handle webfinger and the alias domain stuff thingy