Asking users to pay (and go through UX hassles) to register domain names is not a mainstream user experience. 

It was tried many times including with RSS and didn’t work. 

If your protocol design relies on it, it won’t scale. 

Centralized intermediaries will step in to streamline as Twitter et al did with RSS.

Crypto/web3. Author of Read Write Own

readwriteown.com

I’d push back and say people are starting to understand that if they’re not paying they are the product. Years of ad revenue and selling of data has made people more aware of the incentives. Not the same market. Twitter and Netflix charging drives the point home.

Maybe before was all a 0 interest rate phenomenon l

c/acc - 🏴‍☠️🌊 Bring me that Horizon 🍹
Gold League of Legends player


https://app.icebreaker.xyz/profiles/S8dNdOZBYuvSQxcek2DZD?key=85088

The social internet is made of cats | Director @ Internet Society Hong Kong | Ex-Apple Sr. Engineer | 🇭🇰🇹🇼 | kcchu_.twitter

Ahh kk that makes sense. Misunderstood. I think cuz Dan said that was his biggest fear or key thing that’s yet to be validated so I interpreted this as the same point.

I guess @cdixon.eth is referring to protocols that use DNS names as user identifiers, e.g. Bluesky’s AT Protocol. When people paying to register a domain name, the money don’t go to the product or the protocol, so it is not about user paying for the apps.