@lbkolev

@farcaster has, in theory, the perfect architecture — a clear separation between protocol specification and client implementation. And that's from the beginning..every engineer's dream naming the first client something different than the underlying protocol wasn't ideal but can be argued for (from an engineering perspective) If the first client's name is the same as the underlying protocol then the cognitive load goes to those who might wanna build on top of the protocol, if it differs then it's on the users that sign up

0 reply

0 recast

0 reaction