@mariatta obviously will continue to follow you wherever you go since it doesn't really affect much unless you choose some instance that blocks my instance in which case afaik I wouldn't be able to interact with you (which is why I mentioned fosstodon.org's block of those big instances).
@mariatta I'm not sure fosstodon.org is a great choice, it has a rather strict rule set ("IMO" but I guess you can at least objectively say it's stricter than on most big instances), it restricts two biggest Japanese Mastodon instances... I personally am not so sure it's a great choice (at least for a main account) based on what I've found while looking into it at least.
@foosel @mariatta I think it's overstating how good it is to say that switching is very easy. I imagine that to most people posts and replies they made would be crucial part of migration, especially if the old instance could disappear in future (ideally announced beforehand like with mastodon.technology) and afaik it's not part of the migrated data. Being able to set up redirects and migrate people you follow and your followers certainly makes the experience better but I would say the available migration functionality still misses the crucial part.
Has anyone on #qoto tried using #pinafore? Based on the link it gives, it seems like it requires CORS to be allowed for /api endpoint (which should be the default but maybe qoto is doing something special)?
https://github.com/nolanlawson/pinafore/blob/master/docs/Admin-Guide.md
@glyph @asmodai I mean Armin (mastodon.cloud) and Paul (qoto.org) are both on instances that are blocked by Hachyderm and that block list has no reasoning over why (they even used to block fosstodon: https://github.com/hachyderm/hack/commit/f930a7d4b6e597a109aeaca44e9db7440c1c5668).
Python OSS contributor, maintainer of Red-DiscordBot (http://discord.red)