2 ms·
"Adversarial interoperability" is what happens when you decide to abandon consent as a governing principle for interoperating, because it prevents progress. Peo
by skybrian 7y ago
"Adversarial interoperability" is what happens when you decide to abandon consent as a governing principle for interoperating, because it prevents progress. People complain when unicorns do this.
Even if you had consent in principle, you'd still have to agree to terms for interoperating. In particular, what price and who pays? Or does neither side pay? Consider ISP's and peering agreements.
Even some open source projects will grumble if Amazon uses their software following the terms that are right there in the license agreement. There seems to be an implicit "shadow agreement" that if you use their software to make money, you should give something back. (But that's not what the license says.)
- mfer 7y ago> "Adversarial interoperability" is what happens when you decide to abandon consent as a governing principle for interoperating, because it prevents progress. Whose consent is needed? Open source projects who grumble about amazon created a model where their consent was not required. This is where the ideals of open source don't meed the desires of the VCs paying for the work. It's possible to have a stable business supporting and serving open source but it is hard to do something to meed VC returns on investment with open source. The problem is in the financial model and whose consent is required in that. When it comes to finances things are a little different because the business model is different and so are the regulations. It's also not about open source but about data control. There is the whole idea of interoperating, too. The financial organizations often do not see a benefit to their income by interoperating with their competitors. It might be useful to look at how competitors can come together to collaborate in open source in a way that helps raise all those involved.
- skybrian 7y agoWell, typically you need consent from the service being used. If you look at how the "robots.txt" standard works, consent is assumed even for basic web crawling by search engines. (At least for legitimate businesses; many crawlers do ignore robots.txt.)
- AstralStorm 7y agoThat document should not be considered legally binding. It is not a contract. Robots.txt is not even really a standard, best it was is a draft, set to expire on January 2nd next year. The purpose of the file was to preserve performance, not to hide anything. It targets crawlers not API calls. Consent of a non-single person business entity takes months at the very least, if it ever happens. It's easier for them to deny (incl. lawyers) and intimidate than compete and handle support tickets. Welcome to capitalism.
- skybrian 7y agoIn practice, the crawlers that read robots.txt don't do adversarial interoperability. If a website doesn't want to be in Google's index, they can opt out, and no lawyers are needed to do that.