"Crucially, the value that service adds would not be hosting and backing-up of your email, but rather just the interface and functionality" Yeah but doesn't th

"Crucially, the value that service adds would not be hosting and backing-up of your email, but rather just the interface and functionality" Yeah but doesn't that create a problem, vendor lock-in. Let's imagine we managed to separate data into 2 parts (which I suppose pretty hard), content and meta-data ( by meta i mean service specific information ) Let's say, if I label an email in gmail, it is meta (service specific data), should gmail store this in my pod? - if gmail will store this on their data center, it would lead to vendor lock in. - if gmail will store this in my pod, in a service specific container. Can they use their own spec? Or will they store this with data with extensions ( XMPP all over again ) Now imagine they chose the second one, I migrated to smail (imagine they decided to go for folders instead of labels), do they have to do some migration on my data? What if I go back to gmail again? Or I decide to use gmail one day, smail another? Tbh email is the most easiest situation here, as it has some kind of global standard, Twitch vs Youtube case would be more complicated.