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

Farcaster names like (@v) are actually defined at the protocol level as (@v.farcaster.eth) using a standard ENS CCIP read. 

We truncate the names to (v) when shown in the app because its a bit tedious to type @v.farcaster.eth or show it in every user interface. 

Farcaster names are controlled by us. They're free so its easy to sign up, but we prevent squatting.

Farcaster names like (@dwr.eth) are also ENS names using the L1 ENS standard. 

We show these in full (dwr.eth) so that you're aware they're a fully onchain, decentralized name controlled by the user, and not by Farcaster.

Farcaster has always been fully ENS complaint for all our usernames, full stop.

So mine DegenVeteran.eth is using the L1 ENS standard