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/ 

making data useful with AI. Previously built @stelo to keep you safe from phishing 
benscharfstein.twitter
https://nf.td/ben

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.

Personalization infra @ Superlinked, xYouTube

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?

Fair enough. I understood the point to be that basic web3 primitives enable GDPR principles in ways web2 doesn’t, technical or otherwise

What he lists are technical features - what I’m saying is that the core problem is not technical.