Content pfp
Content
@
0 reply
20 recasts
20 reactions

nicholas 🧨 pfp
nicholas 🧨
@nicholas
Warpcast *is* the app. There aren’t going to be lots of popular interfaces. Power laws still apply. All the important engagement mechanics happen in the UI.
17 replies
11 recasts
40 reactions

nicholas 🧨 pfp
nicholas 🧨
@nicholas
The permissionless Farcaster API will be useful for specialized applications, but there won’t be more than a handful of relevant general purpose frontends and Warpcast will be the biggest.
2 replies
0 recast
5 reactions

Dan Romero pfp
Dan Romero
@dwr.eth
This logic would say that Apple’s first party apps would automatically win. How’d WhatsApp, Telegram, Facebook Messenger, Signal do it?
3 replies
0 recast
3 reactions

nicholas 🧨 pfp
nicholas 🧨
@nicholas
they each control their own backend (protocol)
1 reply
0 recast
0 reaction

Dan Romero pfp
Dan Romero
@dwr.eth
What lesson could one take away from that when building?
1 reply
0 recast
0 reaction

nicholas 🧨 pfp
nicholas 🧨
@nicholas
the FIP process is extremely important. eg i’m never going to get longcasts bc warpcast won’t display them. getting new features cross app might be what matters for sharing control of the protocol such that entities other than warpcast can affect consumption patterns across incumbent interfaces (like ERCs)
1 reply
0 recast
0 reaction

Dan Romero pfp
Dan Romero
@dwr.eth
That’s OSI thinking. IETF thinking is rough consensus and running code.
1 reply
0 recast
0 reaction