0 reply
0 recast
0 reaction
people don't like "build another client", "not a priority", but I'm buying it.
in consumer's eyes, farcaster isn't a protocol - it's a social network. I bet the vast majority is confused between the difference between farcaster and warpcast overall.
in developer's eyes, farcaster is a protocol ofc.
that saying, there is a proportion between two of those that you have to keep:
- too much users, not so many devs – you get a reasonably good twitter clone.
- too much devs, not so many users – you get a dev-only club where normies get lost and even more confused.
and it feels to me like warpcast has the second problem rn. it needs good content creators, artists, bloggers, etc. those who provide non-dev value to make the network's content diversity richer.
i think app client builders should strive more into forking hubs, potentially breaking backwards compatibility and improving the protocol as such by testing out something and proposing a solid FIP, that proves that the change is worth it. 8 replies
3 recasts
39 reactions
0 reply
0 recast
2 reactions
1 reply
1 recast
5 reactions
0 reply
0 recast
2 reactions
0 reply
0 recast
2 reactions
0 reply
0 recast
2 reactions
0 reply
0 recast
3 reactions
0 reply
0 recast
1 reaction
0 reply
0 recast
0 reaction
