4 ms·
force protocols to be open would just about do it. People would trivially write cross-service applications on top and we could have an internet where people can
by Barrin92 6y ago
force protocols to be open would just about do it. People would trivially write cross-service applications on top and we could have an internet where people can freely move data around. Apple and Google would be delegated to the backend and users could choose the clients they want. It's honestly so trivial and uninvasive of a regulatory matter it's ridiculous. We're stuck in the 19th century railroad industry.
- AmericanChopper 6y ago> It's honestly so trivial and uninvasive of a regulatory matter it's ridiculous. At what point do you become compelled to start transforming your web application into an open protocol?
- pydry 6y agoMaybe at the unicorn mark.
- barnabee 6y agoCertainly any company that relies on “safe harbor” style protections or sells online services (alone or bundled with software) as a subscription should be required to fully open and document the protocol.
- AmericanChopper 6y agoBut most SaaS companies don’t make protocols, they make web applications. So I’m not really sure what’s implied by these trivial-to-implement protocols. Having a functional and well documented API isn’t a protocol. An open protocol would be more like a situation where any vendor could implement an “iCloud service”, and any “iCloud client” could connect to any vendors service.
- barnabee 6y agoI don’t agree here. A web application API, properly documented and exposed to any client a participant wants to use becomes a protocol for that service, there’s no difference between CalDAV and the Google Calendar web app’s API except that one is documented, rarely changes, and if offer by a service provider would generally allow any client that implements it to connect, and the other is undocumented and it’s probably against the terms of service to build your own clients. The goal should be to force every API for these providers to meet some minimal definition of a protocol, not to define government mandated standard protocols or force interoperability between services.
- AmericanChopper 6y agoYour definition removes all distinction between the concept of a protocol, and the concept of an API. Google Calendar doesn't implement the Google Calendar Protocol, there is no standards body involved in determining how Google Calendar works, you're not free to go an implement your own Google Calendar compatible service, and Google can change Google Calendar without consultation with anybody. There is no definition of protocol where a single-service API, designed, implemented and published by a single party is a protocol. Google Calendar implements an API. If your argument is that companies should be compelled to publish good API documentation, and allow any client to connect to them, then aside from creating a completely unnecessary system of regulatory moats, and aside from using the wrong words to describe this idea, you're likely to run directly into a 1A violation.
- xmprt 6y agoI think smaller companies tend to have the most open protocols (to the point that it almost becomes a security risk) because they don't have resources to work on unnecessary obfuscation. The protocols might not be documented anywhere but if a website is able to access a backend endpoint then someone else will be able to access that endpoint too. Nothing in the parent comment says anything about requiring good documentation or 100% backwards compatibility.
- AmericanChopper 6y agoYou seem to be talking about APIs rather than protocols.
- somethingwitty1 6y agoThere is a lot of secret sauce in protocols. Those decisions can have serious positive/negative implications on performance and features. Making those easily available to everyone could potentially destroy a business. Don't get me wrong, I've had to reverse engineer my share of proprietary protocols to get behavior I wanted (and would have loved to see them be open), but I don't think I can get onboard with the idea that requiring open protocols is trivial or noninvasive.
- lupire 6y agoThe secret sauce in Apple/Google photos is not the API for accessing the data.
- somethingwitty1 6y agoBut we aren't discussing just these specific APIs/protocols (and I haven't look at them, so I'd have to take your word on that), we are discussing this generally.
- drstewart 6y ago>It's honestly so trivial and uninvasive of a regulatory matter it's ridiculous You can't honestly believe this. Even if one agrees with making some things open protocols, potentialy by law (messenger, social networks), stating "it's trivial" to do such a thing is just the height of hyperbole.
- simonh 6y agoI’m afraid some people really do seem to believe this. Hard to understand, I know. Fixed, regulator defined protocols everyone would be forced to use. Sheesh.
- azinman2 6y agoSo, someone (who?) comes out with a standard, and then everyone just freezes capabilities then? Nothing evolves? Or if it does, it does so very unequally? Already in this announcement is the non-transfer of Live Photos because presumably Google doesn't support it. Apparently they also have a 20k per album cap, which at that point you get different behavior than you're expecting. These are just a few examples of where things go wrong. If we're going to legislate anything, I believe the right way is to force complete data export is made available via a reasonable API/process, which then allows people to independently evolve & progress, and competitors will then need to support (or not) what comes out on the other side. But customers then know they can always extract or simply backup their data themselves if needed.
- fishywang 6y agoAn interface doesn't necessarily limit what the implementation can do. An implementation can well be a super set of the interface (some open standard it supports), with additional features that's not in the interface.
- Barrin92 6y ago>and then everyone just freezes capabilities then? Nothing evolves? Or if it does, it does so very unequally? every client provider can do whatever they want, that'd be the beauty of it. Someone could write a stripped down, privacy respecting Facebook client and charge users five bucks instead of running ads, if that's what users want. Someone could offer a chronological news-feed free of algorithmic meddling, or one that you can fine-tune however you like. That'd would simply be developer and user choice. Just think of RSS-readers or podcast apps or email clients. They're not all equal, but that's a feature, not something gone wrong.
- puszczyk 6y agoWhat does the Facebook get out of it?
- Barrin92 6y agoabsolutely nothing, 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. The purpose such regulation is to benefit consumers, developers, and the health of the market overall. not Facebook. I assume they would be kicking and screaming.
- d0mine 6y agohttp was open once and technically it is open now. Soon the complexity of the protocol will allow only the major corporations to implement it (and it is unclear whether that complexity helps most people).
- deleted 6y ago[deleted]
- ezekg 6y agoIt kind of baffles me that people really want so much regulation. We already have more than enough of it.