Content
@
0 reply
0 recast
0 reaction
Kartik
@slokh
Decided today that we’re not going to be working on /nook anymore. It was originally meant for us to play around with and learn new tech and has served that purpose. We don’t really see a path forward in continuing to build the client, so we’re going to explore some non-Farcaster ideas instead. More soon!
101 replies
191 recasts
826 reactions
Coop
@coopahtroopa.eth
Sad to hear but totally understand and respect this decision. What makes it unviable and what are some reflections you would share for other teams working on clients? Excited to see what you build next! 1000 $DEGEN
1 reply
0 recast
6 reactions
Kartik
@slokh
https://warpcast.com/slokh/0x21314e4d
1 reply
0 recast
4 reactions
Coop
@coopahtroopa.eth
Interesting I guess I take the other side of this - Merkle dependency is good IMO. Makes the need to boostrap social graphs from day one much lower. Focus less on onboarding and more on sticky products since Merkle's biggest focus is user acquisition. What's the alternative?
3 replies
0 recast
0 reaction
Kartik
@slokh
It’s good if it works out, too early to say so. And not something I’m willing to wait to find out over doing the hard work to acquire users ourselves
1 reply
0 recast
6 reactions
timdaub
@timdaub.eth
If you feel like that why don‘t you build a client? I‘m saying this because this argument is the classic cheap talk. Why would anyone want another FC client that they have to log into FROM WC?? That users has the best client already installed, how can they be serious about switching?
0 reply
0 recast
2 reactions
Nico
@sneeks.eth
Alternative I've seen mostly lately is simply favoring FC auth > client. The incentives to build a client aren't aligned, and the ecosystem around the decentralized part of FC is still very early.
0 reply
0 recast
0 reaction
