dylan

Should we rebrand Warpcast to Farcaster?

We separated Warpcast (the app) from Farcaster (the protocol) a few years ago. 

We've heard from many new users that this is very, very confusing. People hear about Farcaster, search in the app store, can't find anything called Farcaster and then churn.

my personal 2c

when I think about Farcaster I don’t think of an app, I think of:
- a community/economy of some amazing people
- common data/identity infra that benefits an ecosystem of apps

I know the protocol’s early enough where a name change won’t be a crazy consequence(espc if the protocol and client apps still have different names), but personally as a community member I’d kinda wish Farcaster would stay as the protocol’s name

engineer @base | /tap /cortex /farhack | dylansteck.com

however at the end of the day I want to see Farcaster succeed more than anything so I’ll be supportive either way 🫡

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

If the problem to be solved is discoverability of the client app due to “farcaster” prevailing as the brand, go with Farcaster as the app name but change the protocol name to something else in order to strive for client neutrality.

Nerds will learn the new name & normies will never need to know it.

devil's advocate position for the protocol name to change instead: merkle is moving the protocol forward and so they deserve the reward for the brand identity that they've built thus far.

let them cash in on that branding by renaming warpcast to farcaster.

rename the protocol so that:
1) it's the nerds who have to learn the new name (not the normies)
2) we signal client neutrality (the client != the protocol)

devil's advocate position for the protocol name to change instead: merkle is moving the protocol forward and so they deserve the reward for the brand identity that they've built thus far.

let them cash in on that branding by renaming warpcast to farcaster.

rename the protocol so that:
1) it's the nerds who have to learn the new name (not the normies)
2) we signal client neutrality (the client != the protocol)

https://warpcast.com/myk/0x4ad5537b