Ben Scharfstein
@scharf
One of the promises of the GDPR was data portability. In practice it’s extremely cumbersome for users to export their data into a competing platform. We need: -API based portability -unique identifiers on entities (for example a unique fb ID, not just a name) -much quicker export times Not sure it’ll happen w/
2 replies
0 recast
1 reaction
Daniel Svonava
@svonava
Beyond speed or even ID misalignment, the main problem is that the platforms didn’t implement a social graph import. Just think about the attacks this would enable.. given that the other side of each connection would have to acknowledge most likely.
1 reply
0 recast
0 reaction
Ben Scharfstein
@scharf
What do you mean?
1 reply
0 recast
0 reaction
Daniel Svonava
@svonava
1. Export connections from FB. 2. Upload to Twitter, where the equivalent is no-directional follow. 3. Twitter has to now check if all those people actually know who you are to confirm the connection. 4. How do they know you are really you? Also, FB supporting this = moat destruction. Why would they make it easy?
1 reply
0 recast
0 reaction
Jeff
@jeffsmith
Doesn’t this prove @scharf’s point?
1 reply
0 recast
0 reaction
Daniel Svonava
@svonava
What he lists are technical features - what I’m saying is that the core problem is not technical.
1 reply
0 recast
0 reaction
Jeff
@jeffsmith
Fair enough. I understood the point to be that basic web3 primitives enable GDPR principles in ways web2 doesn’t, technical or otherwise
1 reply
0 recast
0 reaction
Daniel Svonava
@svonava
Web3 does interesting thing to incentives.. like if your social app doesn’t own the user graph anyway, then it doesn’t need to fight interoperability.. But some things are made much worse, like it’s very hard to delete user data (key GDPR feature) if you run on an immutable database.
0 reply
0 recast
0 reaction
