is there a mastodon-to-pleroma migration guide? is pleroma easy to run in a docker container with a tls frontend (like traefik/caprover)?
alternately, can someone recommend a good managed masto host (i want to continue to use my existing id and domain)
@eris i will keep the domain/id unchanged. i am the admin of this server so whatever IDs are in this database can be moved as-is to the new host.
the fact that fedi software fucking blows and expects me to change my brand name simply because it sucks at internal identifiers is a bug, it's not my problem.
you can have people remote follow your new account to fix it though
わんわん 
@sneak@s.sneak.berlin @eris@disqordia.space it's a limitation of how ActivityPub is designed. but it IS possible to manually migrate in Pleroma's database to move over
- the actor public/private key
- the actor list of followers
- actor list of following
and i think everything should work. most important thing is the private key
@sneak@s.sneak.berlin @eris@disqordia.space it would just be a bit of work if you know what you're doing basically
@sneak@s.sneak.berlin @eris@disqordia.space then your best bet is to either run pleroma on a new subdomain or the same domain but under a different username
@sneak@s.sneak.berlin @eris@disqordia.space otherwise you'll run into a lot of issues, some will see a different public key and refuse to accept notes, followers will be broken and eugh
@sneak@s.sneak.berlin @eris@disqordia.space or you can just say fuck it and leave everyone else to deal with it lmao
@kayden @eris my mastodon instance only looks at l3 ip (which is all the same due to docker userspace proxy) and rate limits everything, so my fedi experience is already super broken without patching masto (no knob to disable per-IP rate limiting otherwise).
at this point i'm just sort of used to masto being busted. i'll port whatever is required from my db to my new host.
@sneak@s.sneak.berlin @eris@disqordia.space wow that's awful
yeah i actually don't think it would be TOO hard, at least just to update the publickey (idk how it works in pleroma, but maybe just one SQL insert?)
and then you could probably import who you're following through pleroma UI, but importing your followers would be harder/or just make everyone refollow you
@eris thanks for the info though; just one more rock on the road of not using twitter. i wish there were non-nerd fedi devs that spend time on earth