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

someone-build

Someone should build a farcaster ENS resolver that resolves vrypan.farcaster.eth to my first verified address. (Yes, there is a problem with ordering, it should be solved too).

Sending tokens/eth to a farcaster user or whitelisting them, etc, should be trivial, without the need for various lookups, frames, tools, or even a farcaster client.

I know that fnames are (or used to be?) .farcaster.id subdomains, but no one is using .id. ENS tooling has advanced a lot since then, I feel that we can have cool .eth subdomains. (Maybe .warpcast.eth, if wc is the source of trust).

I was not aware of Farcaster.eth. I even posted this a few days ago.

I was not aware of Farcaster.eth. I even posted this a few days ago.

https://warpcast.com/vrypan.eth/0x1123b0e9