@jon @Mastodon

I don't think that anyone serious is asking Mastodon to creating NFTs.

What it is being asked of the devs is to separate the technology from the common applications.

NFTs are more than just overpriced JPEGs being sold by scammers, they already work really well to have permissionless domain names and Decentralized Identifiers.

It would be a great weapon against censorship and it could solve the identity portability problem.


@raphael I imagine this is more or less out of scope for @Mastodon though. If they want to implement it, by all means that's fine, but if they don't that doesn't bother me either.

· · Web · 1 · 0 · 0

@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 I'm personally okay with domains being pulled from registrants, if necessary, in existing top-level domain registry model.

@raphael @Mastodon perhaps this should be directed towards Mastodon gGmbH, but I assume solving for censorship-resistance isn't a priority for the project.

@jon @Mastodon not sure what you mean. You are okay with the censorship?

@jon @Mastodon is ThePirateBay a "bad actor"? SciHub? What about Taiwan and Tibet not getting their own top-level domains because of China?

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.

@jon @Mastodon yes, but forks also bring more fragmentation, which is not what you want in a part of the system that depends on network effects.

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?"

@raphael @Mastodon I'm not in a rush to support alternative dns roots on either my own personal devices nor any servers I maintain. I don't know myself what I'd need to change to support resolution of .eth domains but I'll wait until it's done at the OS level if at all.

@jon @Mastodon you wouldn't have to, *if* it was at the application level.

A ENS-enabled Webfinger could just resolve every IP address from any .eth domain by making a CNAME query to the corresponding .eth.link address (which is maintained by the ENS devs)

Sign in to participate in the conversation

jonleibowitz.social is a single-user instance!