Comment by BugsJustFindMe
3 hours ago
> if X has a public API and Nitter is using it
Public as in being visible to all is not the same as public as in allowing use by all. You appear to be conflating the former definition with the latter. For example, my front door is visible to all, but a person isn't allowed to walk into my house without permission.
> Public as in being visible to all is not the same as public as in allowing use by all
Where's the limit of that? Can I have port 443 open with a website behind it but sue anyone that accesses it because the fact that it being visible doesn't mean that I allow anyone to access it?
> Where's the limit of that?
The very obvious answer is that penalty is commensurate with suitable advance notice of authorization limits. It's why there are rules about things like how to post "no trespassing" signs when access boundaries are not otherwise clear. But you're also allowed to notify and make someone leave your property if they wander in.
> but sue anyone
There are two very different kinds of "sue anyone". There's sue them to extract resources from them and there's sue them to make them stop. This is the latter not the former. Treating them as though they aren't wildly different is an error.
You effectively just asked whether I should be allowed to escort someone off my property without harm if they accidentally enter it. Yes, because it doesn't harm them in relation to what they didn't know in advance.
The person is allowed to walk to your door. They are not allowed to walk through your door.
It's a totally different thing.
Indeed. You can look at the shape of the API but not extract things through it. Look, sometimes seeing and using are the same thing, but calling an API, which causes the machine running the API to do work in response to the call, is not the same thing as looking at the API.