Of course keeping your followers is important. But having a new empty wall was a real problem for me.
I didn't know it. Nobody told me, from the people to the interface that I would lose my 3500 messages. It's like having your blog content on another domain in the hands of another host, that can shut your old page down when he wants.
It's the perfect walled garden in terms of content.
Also, the instance where I was had its backup feature down for months. Finally, the followers migration failed at 80 %.
> On this page you can also download a copy of your archive that can be read by any ActivityPub software. This archive includes all of your posts and media. So even if the instance that you are moving from shuts down, as is the case with KNZK, you will still have a copy of all of your posts!
Presumably it's not a technical limitation, since an importer could be written and added by some instances, even if not accepted upstream.
If the lack of import is caused by policy conflict or cost for administrators to review bulk-imported content, does this encourage individuals to have a paid instance to aggregate historical content, e.g. https://masto.host.
A couple of solutions: (a) post them on a website and put a link in your new Mastodon profile, or (b) use something like mastodon.py https://mastodonpy.readthedocs.io/en/stable/index.html to post them to your new account.
Of course keeping your followers is important. But having a new empty wall was a real problem for me.
I didn't know it. Nobody told me, from the people to the interface that I would lose my 3500 messages. It's like having your blog content on another domain in the hands of another host, that can shut your old page down when he wants.
It's the perfect walled garden in terms of content.
Also, the instance where I was had its backup feature down for months. Finally, the followers migration failed at 80 %.