@jon @Mastodon not necessarily. In order to have censorship-resistant domain names, you'll have to make changes at some point of the name resolution stack: either get an ICANN-sanctioned top-level domain (hardest, but endgame for ENS and what it wants to do with .eth), or get OS vendors to be able to resolve ENS (hard, but less so), or (easiest) activity-pub servers can extend their implementation of webfinger.
Meaning, Mastodon devs can do if they wanted to.
@raphael @Mastodon seizures and takedowns are ugly but necessary. a lot of bad actors out there:
Also, bear in mind that pirate bay still exists, despite all of the forced domain changes. Trying to curb them by censorship does not work. It is as "necessary" as it is ineffective.
Say you start having some instances with ENS domains getting popular. Will Mastodon push to block these instances on the grounds of "crypto is bad and we will not federate with them?"
jonleibowitz.social is a single-user instance!