Notices by Jonah Aragon (jonah@mastodon.neat.computer)

@murat IMHO merely "owning" your data in a managed SaaS database is not enough, especially because there is nothing you can do with that data at the moment if you want to leave. It may solve GDPR-type questions about personal data ownership, but practically speaking you're still totally locked-in.

That being said, they did say they plan to support migrations in a reply to my GitHub issue, which is great. I still wouldn't use #Wildebeest until they actually do of course, but it's a good sign!

@feld that's true, although in this case you'd be your own admin. I do kind of wish Mastodon still allowed suspended users to migrate their followers within the 30 days before the account is automatically deleted. I'm sure that would create moderation problems, but it doesn't really seem fair that someone can easily be suspended on one server and lose their entire following for something that is probably totally acceptable on plenty of other servers.

My "position" on #Wildebeest — and really all #ActivityPub software — is as follows: If it lets you migrate your followers in and out, sure, give it a try; If it does not, you should be VERY wary of using it for your important accounts.

Wildebeest does not let you transfer your followers to/from it, ergo it should not be used, lest you find yourself locked-in to Cloudflare's ecosystem forever. Whether or not you like #Cloudflare is irrelevant, you should not tie your fediverse identity to any company permanently.

It's very frustrating for me to see even large ActivityPub implementations that have been around forever not implement follower migrations. Even #Pixelfed doesn't (although I hear that may be coming this year). Anyways... I asked them if they might implement it, but I don't exactly have my hopes up. https://github.com/cloudflare/wildebeest/issues/238