Content
@
0 reply
0 recast
0 reaction
Kyle McCollom
@kyle
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.
19 replies
9 recasts
65 reactions
Vitalik Buterin
@vitalik.eth
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.
3 replies
1 recast
21 reactions
Vitalik Buterin
@vitalik.eth
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.
1 reply
0 recast
6 reactions
Vitalik Buterin
@vitalik.eth
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.
2 replies
0 recast
12 reactions
Paul Cowgill
@paulcowgill
Farcaster follow data is a bottom up set of personal lists, with the extra incentive of being useful on Farcaster. Because of this, it’s more likely to see adoption and be maintained than lists that only are for scam prevention. The unscrupulous L2 should have fewer high-signal follows, ENS handle or not.
0 reply
0 recast
1 reaction
Benjamin Basche
@basche42
It’s funny how everything becomes a list of lists problem eventually
0 reply
0 recast
2 reactions
