I do not understand why Brantly and Esk3nder are picking this fight with @dwr.ethth and @v 

Farcaster is one of the more successful projects to leverage ENS. Instead of critiquing how "ENS-aligned" FC is, perhaps it would be better for the ENS team to reflect on the limitations of ENS that Farcaster had to overcome.

there's some confusion around farcaster names, so let me clear this up: 

- your username on farcaster is ALWAYS an ENS name
- one kind of ens name is the farcaster name (v.farcaster.eth shown in client as @v)  
- the other kind of ens name is the L1 name (dwr.eth shown in client as @dwr.eth)

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links

Oh super interesting! @stevedylandev.eth would this work for the orbiter ens resolution too?

/cal 

Photographer, Artist, Web3 Educator, IP Lawyer, Patent Agent, Explorer 📸⛰️✨ 

 Building /flowcast with /mindfulness 🌊

https://wanderloots.com/links

Ah got it, was just thinking if there was a way to auto resolve anyone’s orbit to farcaster name if they don’t have an L1 ENS

Very possible! It might be tricky since Merkle owns the top level ens name but there could be something there