how would you define client diversity?

because warpcast, jam, and discove all feel like different flavors of the same app — with marginal advantages in functionality between them. kinda feels like the myspace v facebook v friendster era.

fwiw, how did facebook set itself apart? controlled growth.

/ted | exploring the onchain frontier | surfing @ venice, ca | eating @ gjusta / gjelina

think this has been said before but

a) without controlling invites & onboarding apps can only target this community right now
b) few app types that people use two times a day (req for vc $)
c) many apps will start with basics and add layers of new things on top; apps will look similar then diverge as they mature

Building FOSS via @frames, /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id

wouldn’t say I was defending but rather explaining what I think the fundamental dynamics are - think the differences will speak for themselves, and then what works will be copied by others. 

discove is trying to users in control of what they see and how they participate in social apps - by allowing feed creation

also, this cast was a perfect layup for you to highlight the differentiators of discove — both today's features and your vision for future features. 

idk why you chose to defend the similarities instead of pointing out the differences :)

download meeeee @ blobs.lol;
win up to $75 every week!!!

yes, im aware of all the above. it doesn’t answer my question of how you would define client diversity.

if apps are different but the impression is that they’re not, then there’s a branding/value prop problem.

if apps are the same, then A feels like a crutch. behavior/needs vary widely across users (eg @blobs)