Content
@
0 reply
0 recast
0 reaction
Sacha
@s4cha
Hot take on farcaster: the larger it’s going to get the more likely it’s going to fail. Basically: supporting the protocol doesn’t deliver the same value to all clients. For small clients it’s 100% value. For medium clients, it’s still quite good (1/x)
1 reply
0 recast
0 reaction
Sacha
@s4cha
We all know this; they tap into content, social graphs, dms that would have been impossible to bootstrap. Things are 100% different for large clients. For market leaders it’s negative sum to support the protocol. You just make it easier for competitors to take market shares, you’re just diminishing your nfx.
1 reply
0 recast
0 reaction
Sacha
@s4cha
Imo, if farcaster takes off, the largest clients will at some point start adding features non protocol-native (i.e. snap-like instant photos), then be a bit more aggressive (maybe a kind of content that’s only on their app?) then totally drop it. It’s a huge win for a client: you smoke competition. You create nfx.
1 reply
0 recast
0 reaction
Sacha
@s4cha
Discussed with this with a few farcaster pros, no one has been able to counter this yet. Thoughts @dwr.eth @v?
1 reply
0 recast
0 reaction
Varun Srinivasan
@v
why do email clients still work with each other?
1 reply
0 recast
0 reaction
Sacha
@s4cha
I believe that’s because email is something where you have a lot of no-front-end / auto messaging actually. That’s 90% of the usecase for mails, and you can’t get that go through solely your client.
1 reply
0 recast
0 reaction
Sacha
@s4cha
Also email is ultra light, single use case. A social media does a ton of things. I.e. as I was mentioning, you could be just adding special DMs to get started. I can’t think of any feature that could be non-protocol-based for email clients to add.
1 reply
0 recast
0 reaction
Sacha
@s4cha
Thoughts?
0 reply
0 recast
0 reaction
