Earlier quoted context omitted.
That's not true, you can mistakenly receive data you're not authorized to have (might even be criminal to have!) > That's entirely different from gaining unauthorized entry to a system and copying out files that were never publicly available to begin with. That's not the sum total of hacks, if you have publicly accessible password-protected PDF and guess the password as 1234, that's a hack. Copy& paste of black boxes…
> you can mistakenly receive data you're not authorized to have (might even be criminal to have!) Not the layman, at least to the best of my knowledge. Yes, certain licensed professionals can be subject to legal obligations in very specific situations. But in general, if you screw up and mail something to me (electronic or otherwise) then that is on you. I am not responsible for your actions. > if you have publicly a…
Are you not aware of content that is criminal to possess? Like CP is the most common example.
> I am not responsible for your actions.
I've already addressed this confusion of yours - this is NOT about your responsibility for someone else's actions, but about your own actions and whether they constitute a "hack".
> You are the only one using the term "hack" here. Please note that I had responded to your "limit/lack of authorization" phrasing. Nothing more.
Please open a dictionary for the word hack to understand this conversation! And note the word "authorization" in the definition.
> However that isn't what (I understood) us to be talking about - ie legal authorization
Understandably you're confused, the legal limit is your own making, authorization is way broader than that.
> I'll note the ambiguity of the term "hack" in this context
Exactly!!! Keep looking into the definition to resolve the ambiguity!
> You seem to be failing to clearly differentiate
No, your differentiation is wrong