Farcaster

since apparently the "build another client, not a priority rn, doesn't drive long term growth, etc" is the default response here

(despite the general sense that channels are a rushed, underexplored feature (potential new primitive) where the lack of prioritization and thoughtfulness has led to increased friction and a worse NUX)

is anyone building a channel-focused client? 

i'm incredibly excited about the promise of channels and promise to dedicate a portion of my time, energy, and resources to exploring this with you and supporting you

i am a force of nature, as some of you may know, especially when i'm motivated by both the mission and someone telling me i'm wrong

zinger

Surprise: building consumer apps is hard as fuck 🤗

Hard truth: most of the replies to this complaining about how channels aren’t in the protocol are just cope

Channels not in the protocol? Build your own channels. Direct casts not in the protocol? Build your own direct casts. That’s what Warpcast did.

What you’ll come to realize (after a bunch of wasted time and effort) is that channels are a product problem, not an engineering one

Apps that only focus on one or a few channels don’t make sense, not enough of a wedge or retention mechanism, partially due to how early we still are but also people don’t want to download a separate app for each of their interests

Apps that focus on all channels and encourage you to check them individually are too much work for the user (see Discord, Telegram, etc) so you end up back with an algo feed to surface the most interesting content in one place

Building a social app is a retention (and GTM) problem for the most part, not a technical one — and it’s hard as fuck

Hard truth: most of the replies to this complaining about how channels aren’t in the protocol are just cope

Channels not in the protocol? Build your own channels. Direct casts not in the protocol? Build your own direct casts. That’s what Warpcast did.

What you’ll come to realize (after a bunch of wasted time and effort) is that channels are a product problem, not an engineering one

Apps that only focus on one or a few channels don’t make sense, not enough of a wedge or retention mechanism, partially due to how early we still are but also people don’t want to download a separate app for each of their interests

Apps that focus on all channels and encourage you to check them individually are too much work for the user (see Discord, Telegram, etc) so you end up back with an algo feed to surface the most interesting content in one place

Building a social app is a retention (and GTM) problem for the most part, not a technical one — and it’s hard as fuck

https://warpcast.com/zinger/0xa6906bb7

/new-york by day 🗽 /latenightcrew by night :) Fan of eating tacos and bringing people together, often at the same time 🌮 oh and /untzuntz 😈

‘Just build your own ______’ is a protocol problem, ppl expect some bare minimum standard of primitives and the lack of them is often cited by ppl for not building or extending products here 

I really think the buoy from frames has contributed to some arrogance