[lbotos]

"By accessing or using our APIs, you are agreeing to the terms below." <- https://developers.google.com/terms

"By accessing or using Microsoft APIs, including within a software application, website, tool, service, or product you create or offer to Customers (your "Application"), you are agreeing to these terms and to comply with any accompanying documentation that applies to your use of the Microsoft APIs ("API Terms") with Microsoft Corporation ("Microsoft", "we", "us", or "our"). You represent and warrant to us that you have the authority to accept these API Terms on behalf of yourself, a company, and/or other entity, as applicable." <- https://docs.microsoft.com/en-us/legal/microsoft-apis/terms-...

Again, I'm not a lawyer so this could be unenforceable, but I have to assume everyone does it because it's at least somehow useful.

[pbasista]

I am also not a lawyer. But it seems to me that public usage of any publicly accessible resource can only be restricted by law.

Regardless of what some ToS say, they can only apply to the people who explicitly agree to them. It would not make any sense, in my opinion, to assume that such an agreement is implicitly given by merely using the resource.

Consider, for example, a situation when someone places a bench into a public park for public use. The conditions under which this bench can be used are defined by law in a sense that, as a property it should not be damaged, stolen, etc. But nothing more.

The owner of this bench might create a ToS in which they might state almost anything. For instance, they might have a clause saying that by sitting on this bench you agree to donate $10 to their cause.

But if a person sits on this bench and does not donate, they did not break any law. They merely did not agree to the ToS of this bench and used it, in accordance to all applicable law, as any other publicly accessible bench.

[lbotos]

While the internet may feel like a public park, when you access twitter's API you are connecting to their servers, which are not owned by the state. They are owned by a private entity.

Private entities can make whatever rules they want for their property as long as those rules don't break laws.

Twitter says don't reverse engineer. You reverse engineer. They block you. They can do that. If you actually break a law and cause damages with your reverse engineering, they can consider suing you. They can do that too.

If you are ignorant to the terms in which someone is offering a service to you then you are only exposing yourself to unneeded risk.

[pbasista]

> Private entities can make whatever rules they want for their property as long as those rules don't break laws.

Yes. At the same time, people can use whatever publicly accessible resource in any way they like, as long as they do not break any laws.

The crucial point here is that the object of this discussion is a publicly accessible API. That, by design, comes with some elementary rights which cannot possibly be revoked by the fact that the API's provider puts something into their ToS. One of such rights is the right to use these APIs.

When someone uses these publicly accessible APIs and based on their experience then makes logical reasoning and conclusions about how they work, it might be considered as reverse engineering. But I cannot imagine how could a thought process be legally forbidden by any ToS in any way.

When someone then publishes their findings about the functionality of this public API, they are merely publishing the results of their reasoning based on facts that are publicly available. It is in essence a research result based on publicly accessible input data. Again, I cannot imagine how could such an activity be legally forbidden by the existence of some ToS.

> terms in which someone is offering a service to you

This service is offered as a publicly accessible API in the first place. The fact that someone might enter into a contractual relationship with the API's provider and therefore have their rights restricted is irrelevant for the purpose of this discussion.

Its main topic is the usage of this publicly accessible API without any contractual agreement.

If someone claims that a mere usage of some publicly accessible resource immediately constitutes entering into some contractual agreement, such provisions need to be supported by the law. And I am unaware of any legal obligations to agree with the publicly accessible API provider's ToS before using the API.

The API provider can put almost whatever they want into their ToS. The important part is whether or not it is backed by the law.