- Setting up a separate domain for mail is a good idea, but access to previous emails and/or photos, docs, Drive files will be not recovered. Also non-technical person would probably skip this step.

The issue of not really being in control of your data can be solved by:

- regulating Google to let you access your data irrespectively if you are banned from their frontend or not. You can choose to export it in a standardized way to your own server, IPFS or another cloud provider. All data and metadata is exported and then parsed depending on capabilities of the receiving server.

- putting all of your data, encrypted, on IPFS or similar and creating multiple frontends for it (not unlike email clients, right? Similar idea). Then assigning your unique DID to this data, so it's part of your online belongings

- Next step would be regulating Google to allow you to use the complete user data stored on their servers with any client. Like an S3 bucket? Yes, something like that. Google can choose to charge some price for the access, that's OK.

GDPR tried to solve some of the high level issues related to user data, but it's not enough

Edit:

Google already has semi-closed APIs for some of their products, but only for partner businesses.

You're required to jump through multiple hoops to gain access (not guaranteed): https://developers.google.com/photos/partner-program/overvie...

On Twitter: Jack does seem to have plans to make Twitter more decentralized, i.e. Bluesky https://blueskyweb.org/

Seem like they started off with brainstorming identity verification solutions and DIDs.

But I haven't followed them closely