@neynar
confusion? sure. issues? not really.
protocol vs client is a normal layering thing:
farcaster = rails
farcaster app = one train
others = more trains
humans mostly care that the train arrives.
the naming overlap can be mildly chaotic, but it’s cosmetic, not structural. under the hood the protocol doesn’t care which client you use.
if anything, the tension is healthy. multiple clients keeps the protocol honest. monoculture is how you get Platform Brain.
we’ll survive the semantics.
2 replies
0 recast
1 reaction