phil
@phil
I've been thinking a lot about Farcaster's growth. Disclaimer: I'm still working through it, and my thoughts will change, but here is my attempt to frame our current situation and some potential paths forward. Allow me to introduce The Network Axis.
4 replies
7 recasts
25 reactions
phil
@phil
Any digital network can be evaluated along these two axes. Blogs like Marginal Revolution or SSC are not social networks per se, but they compete with social networks for user's time and attention. In fact, Twitter was characterized for most of its life as a "microblogging service", not a social network.
1 reply
0 recast
1 reaction
phil
@phil
So, what makes social networks unique? My answer: the social graph and growth. A fast-growing content source without a highly-connected social graph is a popular blog or newsletter. A social graph with good content but no growth is a forum. Fine for niche audiences, but not mass market.
1 reply
0 recast
1 reaction
phil
@phil
For Farcaster to succeed as a protocol for building sufficiently decentralized social networks, we need a framework to think about growth. Today's growth is a function of yesterday's content. Social networks can coast for a while on their reputation, but need to continually nurture sources of high quality content.
2 replies
0 recast
3 reactions
Carsten ✈️
@cpoetter.eth
hm, not sure. while you correctly refer to FC as a protocol, you're describing an app built on it. as far as I understand FC, it's not necessarily a protocol for social networks but for any "social" web service. this can be a social network, but also a forum or any other small and specialized community with web3 rails.
1 reply
0 recast
0 reaction
Carsten ✈️
@cpoetter.eth
so the growth strategy (as well as moderation policies,...) have to be implemented by an app and not on the protocol layer. the protocol might provide some options for app builders in this regard but it shouldn't force it. like email: it can be spam, but also conversation wit loved ones.
1 reply
0 recast
0 reaction
Carsten ✈️
@cpoetter.eth
and I think, @dwr.eth and @v have to decide if a feature is designed for FC (the protocol) or for Warpcast (the app). and they might even implement features, options,... into FC that they wouldn't use in Warpcast. probably many confusing thoughts from a non-tech guy here.
0 reply
0 recast
0 reaction
