Content
@
0 reply
20 recasts
20 reactions
nyc-crypto-cabal-kid
@zinger
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
7 replies
0 recast
115 reactions
Michael Pfister
@pfista
This feels directionally correct for channels but having a harder time seeing why it is the case for direct casts, especially wrt b2b farcaster apps. To narrow the problem through Buoy's lens– our customers are teams on Warpcast and they have to manage customer issues via DC. Building our own DC system wouldn't solve this, because end users don't use buoy. End users DC founders who then have a hard time managing it all between their team, and that's what our product aims to solve.
0 reply
0 recast
1 reaction
