

I mean DNS is always the issue… but then that’s kind of the double edged sword as well isn’t it?
Conceptually 4 options come to mind.
-
DNS as current - weakness domain name changes or DNS outages or poisoning
-
IP address - Issues, migration etc… some instances may need to move services etc…
-
SSL private/public keys - probably the strongest I’d imagine. only real weakness I can see is… 1. it has no ability to find a server, and I guess if a server is hacked and it’s private key is stolen, federated servers would not be able to spot the imposter.
I do think 3 might be the strongest option. I don’t know anything on how lemmy etc… works. I’d imagine a strategy would be, When A and B federate with eachother, A records B’s Domain name, IP, and public key (and B gets A’s as well), if DNS goes down attempt recorded IP. If neither work wait for an incoming connection and if the new connections public key matches an existing public key, it assumes the identity.
But as far as the user side I don’t really know. Obviously we can only match users as their domains. I can’t imagine how I could find you again with gammaray@sh.itjust.works when sh.itjust.works domain is unregistered.

I mean it’s a mixed bag… I get the idea of nothing should be removed, blocked, downvoted etc… as the ideal of free speach.
Right up until you look at every platform that explicitly avoids it and goes full “We’re all about free speech!”.
IE huge problem is, the first people to jump to those platforms, are the ones that have been banned for good reason from everywhere else. Which of course means… nazi’s come in droves Reasonable people that either have less borderline, or perhaps no borderline thoughts get there… see 500 posts from nazi’s, and head for the door imidiately, until it just turns into a nazi echo chamber.