Content
@
0 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
Have had a few people ask: how come Warpcast is moving so much faster? 1. @v has led a huge push to ruthlessly prioritize on everything we work on 2. We stopped having two priorities: making the protocol permissionless and building new app features—the entire team is focused on growth now.
17 replies
6 recasts
208 reactions
polymutex
@polymutex.eth
Is there a point at which the discrepancy in feature parity between Warpcast and other Farcaster clients becomes a problem?
2 replies
0 recast
0 reaction
Dan Romero
@dwr.eth
Why?
1 reply
0 recast
1 reaction
polymutex
@polymutex.eth
Because a monopoly client has a strong incentive to eventually subsume the open protocol it is built on; that's the story of web2. We're obviously very far away from this happening for Farcaster/Warpcast, and I don't think this would ever happen under your leadership. I'm only musing about the question in the abstract.
1 reply
0 recast
2 reactions
Dan Romero
@dwr.eth
Sure possible in theory In practice it’s way more likely to die from lack of usgage If we get to millions of DAU then we will have another well-funded client.
2 replies
0 recast
3 reactions
Wilson Cusack
@wilsoncusack
I'm curious how you think about, At one point twitter had open APIs and client diversity. Then Twitter shut those APIs down and killed the other clients. If Warpcast has monopoly and somedays decides to abandon Farcaster protocol, does it go the same way?
1 reply
0 recast
1 reaction
polymutex
@polymutex.eth
Fully agree. Another failure mode is that usage does pick up, but a web2 giant decides to make their own client and eventually outpaces more ideologically-motivated teams, kind of how Chrome took over Firefox. Either way, planning to do my part towards 1M DAU 🫡
0 reply
0 recast
0 reaction
