I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

How come dapps and such don't seem to integrate with imported dns->ens names by default? I'd always assumed that once it is imported it's in the same registry and treated the same as a standard .eth but that doesn't seem to be the case (e.g Farcaster doesn't support non eth TLD)

Enthusiastic about web3 domains. Imported a web2 DNS address into ENS and voila, got my grail domain, Jack.top

Yea that’s a common mistake by devs that we’re trying to educate (fwiw Farcaster’s was intentional, they have their own reasoning)

Many dapps basically have 

if (input.endsWith(“.eth”)) {
  // try to resolve ENS name
}

When really they should treat any dot-separated string as a potential ENS name

Here’s a recent example https://github.com/scaffold-eth/scaffold-eth-2/pull/563

I feel you. Good to know with Coinbase cc @jessepollak

Yeah the two I've come across so far are the main coinbase exchange doesn't recognise my Jack.top name as an eth address, and Farcaster. 

It's a real shame Farcaster don't, and a shame it's actually possible for 3rd parties to discriminate based on it. It makes them feel like 2nd class citizens in ENS land :(