Post APOVSTmi3Mz3G9UeMi by davidstosik@mstdn.jp
 (DIR) More posts by davidstosik@mstdn.jp
 (DIR) Post #APOVSRH5NyV1TUgMnQ by davidstosik@mstdn.jp
       2022-11-08T03:01:20Z
       
       0 likes, 1 repeats
       
       So, it sounds like picking a #Mastodon #instance is a bigger deal than every one makes it...See, when you migrate Mastodon instances,  you leave your posts behind...You can of course export your posts from an instance before leaving it, but there is no way to reimport them in the new instance you join.(...)
       
 (DIR) Post #APOVSTmi3Mz3G9UeMi by davidstosik@mstdn.jp
       2022-11-08T03:01:38Z
       
       0 likes, 0 repeats
       
       (...)In other words, you entrust the long-term availability of your posts to the instance you're currently in, with no possibility to transfer that responsibility to another instance. (Your new instance will only be responsible for what you wrote there.)
       
 (DIR) Post #APOVSVNy6KNiDzvv4y by davidstosik@mstdn.jp
       2022-11-08T03:18:42Z
       
       0 likes, 0 repeats
       
       If an instance stops being maintained or updated (mstdn.jp is 2 releases behind) or its performance drops, and it doesn't work as you expect it to (@debirdify and @moaparty do not work on mstdn.jp), and you decide to migrate, then you're forced to leave your old content behind, and hope your old instance's maintainers will keep it up.If an instance's maintenance team decides to take it down, then your content is at their mercy...