
mildredsally
@mildredsally
5 replies
3 recasts
43 reactions
0 reply
0 recast
0 reaction
225 replies
843 recasts
2667 reactions
0 reply
0 recast
0 reaction
5 replies
6 recasts
47 reactions
0 reply
0 recast
0 reaction
6 replies
8 recasts
90 reactions
0 reply
0 recast
0 reaction
7 replies
12 recasts
75 reactions
0 reply
0 recast
0 reaction
6 replies
3 recasts
17 reactions
0 reply
0 recast
0 reaction
7 replies
10 recasts
83 reactions
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
14 replies
4 recasts
25 reactions
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
7 replies
1 recast
34 reactions

My 2c on Farcaster vs Warpcast & how it relates to building a multi-client protocol:
π€·ββοΈ Clients donβt always have to read all state or perform all writes. ETH has multiple client types, and FC protocol can too.
π Under this framework, the protocol already has a much richer ecosystem of clients than it gets credit for. All mini-apps (FKA frames) are clients utilizing some combo of FC's social graph, content, associated wallets, DCs...etc.
π I view Warpcast as a hub through which we view & interact with the FC protocol, not some global reference implementation every other clients has to emulate to give or get value. This has already been true for some time now, and rebranding the app to Farcaster just makes it more clear.
π«΅ Permissionless data (and to some extent, writes) means anyone can still build any type of client they want, including one has the exact functionality as Warpcast, just like anyone can choose to run/write any ETH client they want.
Thx for coming to my TED talk. 1 reply
8 recasts
66 reactions