|
|
|
|
|
by zug_zug
905 days ago
|
|
Well -- I'm not. I think it's almost an intuitive tenant of non-monopoly -- interoperability. Also, in practice, I think maybe less than 10% of this site doesn't believe that enshitification is real. Forcing interoperability via open-api standards is the only practical solution I can see to enshitificatin. Such as: any client can call imessage and register a webhook to receieve messages at or download messages if it has username, email, 2-factor token, etc. Or such as any user can access reddit/facebook/whatever with any client and can export their data to a competitor. (I'm an iphone user for the record, not that it matters) |
|
Interoperability with printer cartridges and game console controllers is different than mandated always-on servers.
In the former cases the only cost to the OG business is the opportunity cost of losing customers, and yes, that's just intuitively anti-monopoly rules.
But what is being considered here is the idea that a company should be obliged to allow another business to send them large amounts of traffic without paying anything, while simultaneously charging their own users for access to the original company's servers. This case is much less clear cut: you're essentially saying that, in the name of interoperability, any business that runs a platform is obliged to support some indeterminate number of other businesses at their own expense.
If you mandated interoperability but allowed charging the other businesses for server access, that would be a step in the right direction, but you're still mandating that the original business engage in a business relationship that they would rather not engage in. Still very much less clear cut than the hardware cases.