KMac🍌 ⏩
@kmacb.eth
Been thinking about the Warpcast ↔ Farcaster naming debate. If you don’t love the Warpcast brand, change it — that’s an app-level decision. But I don’t think this is a market problem. Feels more like an internal team identity crisis than anything external. The confusion isn’t from users — it’s from how the Merkle Manufactory team talks about what they’re building. The framing is nearly always protocol-first, never app-first. That works for devs, but it’s disorienting for regular users trying to make sense of what they’re using. If the concern is app adoption or brand clarity, the answer isn’t to rename the protocol. It’s to embrace the app. Let Warpcast be Warpcast — and speak to people like it’s an OS for the crypto social internet. Let Farcaster be the rulebook underneath (verify / store / forward… oh snap! consensus). It’s still early. There are wrong moves. Let’s not collapse layers just because they’re currently close. Growth will pull them apart anyway.
5 replies
0 recast
12 reactions
shazow
@shazow.eth
Doesn't help that a lot of what's interesting about Farcaster are actually Warpcast-only features.
1 reply
0 recast
0 reaction
KMac🍌 ⏩
@kmacb.eth
It's been confusing for a long time. A few things I believe in - Apps & Protocol have different names - App specific features are encouraged - Protocols are not entities w staff - Apps should not be forced to know how each other are doing - I believe in the sweet spot, soft core pornography, opening your presents Christmas morning rather than Christmas Eve, and I believe in long, slow, deep, soft, wet kisses that last three days.
1 reply
0 recast
1 reaction
