@Lyx@rher You can't just reinstall Pleroma on the same domain, I'm not so clear on the technical details myself but there are.. problems that arise with instances that have already federated with your old install if you try that.
You could probably just purge all of the old posts from db, but that would take a long time and would probably be unnecessarily complicated
@nyanide@rher the thing im unclear about, why dont u guys just purge it all and start eith a clean slate instead of purchasing and setting up a new domain¿
@tinosoft@Lyx@nyanide@rher@sun you definitely can do a reinstall on the same domain, but other software might not accept users with the same name if you don't have their rsa keys backed up
@i@Lyx@tinosoft@rher@sun Yeah the keys thing, you could just do a Matrix Server Admin moment and copy all of the keys over to a new install of Pleroma. I guess it'd mostly work in theory? There'd probably be a few weird issues like instances sharing posts that no longer exist and new instances actually getting them.
@nyanide@Lyx@rher this is less of a problem these days. Pleroma instances will attempt to refetch keys if it receives signed activities that don't validate due to key mismatch. So key changes are possible. I think Mastodon does similar now.
@feld@Lyx@nyanide@rher huh, neat, so domain reuse is definitely viable, and seems like pleroma it self was the thing holding it back from happening, instead of worries about people impersonating old instances
checked the misskey/mastodon code/issues and they definitely do key eventual refetches once their ~24h caches expire
@nyanide@i@feld@rher i had an interesting idea at inr point, to evade block lists, could u possibly set up a rotation of tor domains since u dont have to buy them¿ like to auto generate a new one weekly¿ i was figuringbdoing it on cloud would make it possible rather than a physical server location. I wouldnt do it but i thought it was an intereating idea
@i@Lyx@feld@nyanide@rher >there's a few public https to tor gateways people have used for that I think I used one of them (onion.ly or something) to block evade, it was pretty slow and also embedded some analytics scripts. tor.observer is apparently fresher and more stable but some pedophile figured this thing out as well so I chemo'd it just in case.
@Lyx@feld@nyanide@rher there's a few public https to tor gateways people have used for that, it's not too hard to write software that can work on a wildcard certificate *.instance.domain giving you infinite domains to work with too
but then people block the root domain including all subdomains, so you're stuck with buying multiples of the cheapest possible domain and cycling through them
and things like pleroma don't do multiple domains, so it's a bother