df pfp
df
@df
Had a call with an industry titan in product management yesterday. He asked me in which ways web3 social can be: Cheaper, Faster or Better than web2 social? I had an answer that I thought was compelling, but his follow up questions were challenging. I'd be (genuinely) curious of what you think is the strongest answer
31 replies
0 recast
0 reaction

df pfp
df
@df
My answer was: 1. Bottoms up innovation from the community and therefore much faster innovation feedback loops and 10x better apps. 2. Better apps because apps no longer need to battle the cold start problem with building a community/network effects. 3. Better app experiences due to portability of your social graph
7 replies
0 recast
0 reaction

Cassie Heart pfp
Cassie Heart
@cassie
Regarding point 1: the innovation spreads beyond the protocol — in trad social, the apps are defined by the service, the boundaries set by the provider dictate the domain and thus the range of features that can exist. In decentralized social it’s more bidirectional —
2 replies
0 recast
0 reaction

Naveen pfp
Naveen
@yateagle
this feels forced to me. This has been done in web 2. Remember facebook apps? At the beginning it was crazy open. You could spam the social graph etc. It ended up adding some value, but not enough for FB who realized that users don’t like app spam, and they can make more $$$ via ads
0 reply
0 recast
0 reaction

MC10 | Bankless Consulting 🎯 pfp
MC10 | Bankless Consulting 🎯
@mc10
Your #1 and #3 are valid (and strong) answers in my view. The cold start problem solution requires more discussion. In particular, #3 is something that simply cannot replicated by web2. I'd love to jam with you on this over a call.
0 reply
0 recast
0 reaction

moreReese pfp
moreReese
@morereese
Portability is a huge game changer. Users have only existed within walled data gardens. Once that mindset shifts to data ownership, quality and UX will raise exponentially
0 reply
0 recast
0 reaction

mk pfp
mk
@monishkumar
As a user, biggest advantage is data portability. Example is email - I can use any client that matches my needs. For social - it will be the interface, the algorithms they choose and what they choose to differentiate with their app. Things like Twitter shutting off third party apps with no warning/info can’t happ
0 reply
0 recast
0 reaction

khaw pfp
khaw
@khaw
For cold start problems tho, I kinda doubt it. This is based solely on my experience convincing my university friends but I have learned that web2 people use social media mainly for content and to connect with friends. They stick with a few social groups and see no point in moving to web3 social for now based on 1&3
0 reply
0 recast
0 reaction

khaw pfp
khaw
@khaw
I 100% agree with your point 3. I was once presenting web3 social in front of non-web3 users (age around 30+) and the point about portability is a clear value prop they can understand right away.
0 reply
0 recast
0 reaction