Product

As a user with a Farcaster account, I'd rather see someone's Farcaster username in your app than their ENS.

I interact with people's Farcaster username, not their ENS.

The namespace more closely associated with online identity and my social graph will win.

summoning /daylight | kylemccollom.com | we are hiring: careers.daylight.xyz

I don't think we have to choose between the two paths?

@dwr.eth isn't the plan already that farcaster names will become accessible as an ENS subdomain via CCIP, similar to how status works/worked with *.stateofus.eth?

We're going to get namespace competition via L2s anyway, ENS just makes it interoperable.

Ideally we've have community-managed lists for that sort of thing, similar to the list metamask maintains form scams.

No need for fancy governance: if a list itself becomes abusive (eg. someone's legit account gets declared a scammer because the list admins don't like their politics), the community can just fork.

The vitalik vs vitalik.eth thing is interesting, but it's also not a namespace issue: there's the possibility of eg. some unscrupulous L2 getting `optimism` on FC. The natural solution is for frontends like Warpcast to censor or put a big warning on impersonating accounts.

Yes Fnames are a centralized (for no) CCIP Read ENS name. Like cb.id

My view is many interoperable namespaces thanks to ENS is ideal.

ENS on L1 will be akin to domain names vs. cheap / free L2 usernames for a variety of apps / services feels optimal.

I don’t subscribe to 1 username rule them all.

Fnames are already ENS subdomains using CCIP, I just don’t think it’s well known. I’m not sure they resolve to any address yet either.