> it would subject their applications to genuine competition (they could of course still offer their own client) and destroy their walled garden, which is the entire point.
Hmm. At least in the case that the OP was taking about -- third-party Facebook clients -- I don't think it would "destroy their walled garden" any more than third-party Twitter clients did back when those were meaningfully a thing. Standardized APIs aimed at enabling full-featured third-party social network clients wouldn't really contribute to a robust market in competing social networks; they'd just contribute to a robust market in, well, third-party social network clients.
What it seems to me you want is a couple steps beyond data portability, which honestly really isn't enough on its own. What I actually need is a way to import the user's social graph from Facebook or Twitter. That's arguably how Instagram bootstrapped its success initially: if you gave it your Twitter account, it would download all your followers/following info. (And, of course, that's why Twitter shut down that API after that.)
"But doesn't that violate GDPR?" someone is raising their hand to say, and: yes. GDPR as written does help protect privacy, but it's also an incredible boon to social network incumbents: it under it, your social graph can't be treated as your data, because by definition it contains personally identifiable information about all your contacts. For your regulation idea to be meaningful, GDPR and similar privacy regulation around the world would have to be overhauled -- if all the "open API" can do is import/export my personal data sans social graph, it becomes little more than a backup mechanism and a convenient way to fill out registration forms.
Hmm. At least in the case that the OP was taking about -- third-party Facebook clients -- I don't think it would "destroy their walled garden" any more than third-party Twitter clients did back when those were meaningfully a thing. Standardized APIs aimed at enabling full-featured third-party social network clients wouldn't really contribute to a robust market in competing social networks; they'd just contribute to a robust market in, well, third-party social network clients.
What it seems to me you want is a couple steps beyond data portability, which honestly really isn't enough on its own. What I actually need is a way to import the user's social graph from Facebook or Twitter. That's arguably how Instagram bootstrapped its success initially: if you gave it your Twitter account, it would download all your followers/following info. (And, of course, that's why Twitter shut down that API after that.)
"But doesn't that violate GDPR?" someone is raising their hand to say, and: yes. GDPR as written does help protect privacy, but it's also an incredible boon to social network incumbents: it under it, your social graph can't be treated as your data, because by definition it contains personally identifiable information about all your contacts. For your regulation idea to be meaningful, GDPR and similar privacy regulation around the world would have to be overhauled -- if all the "open API" can do is import/export my personal data sans social graph, it becomes little more than a backup mechanism and a convenient way to fill out registration forms.