I’m not an attorney or anything, but the relevant federal statute is explicitly about unauthorized access of computer systems (18 USC 1030).
Opening someone else’s laptop and guessing the password would absolutely fall under that definition, but I think it’s very much questionable if poking around a document that you have legitimately obtained would do so.
If someone sends me a document with text in it that they meant to remove but didn't and then I read that text, I haven't hacked anything they're just incompetent.
Hacking is unauthorised use of a system. Reading a document that was not adequately redacted can hardly be considered hacking.
Or in case some folks find the addition of a computer confusing here, if someone sends you a physical letter and they've used correction tape or a black marker to obscure some parts of the letter, and you scratch away the correction tape or hold the letter up to a light source to read what's underneath, have you committed a crime?
I'm not a lawyer, so I don't know what the law has to say about this. But I do have at least a small handful of brain cells to rub together, so I know what the law _should_ say about this.
Precisely. If someone wants me to sign a contract on acceptable use of resources (like an agreement not to reverse engineer their software) they send me then that's another thing.
Absent that excluding other default protections like copyright, what I do with it should fall under the assumption of "basically anything".
If this were prior to 2021, I would say the CFAA could be violated so long as the property owner's _intentions_ were for that information to only be accessible to certain users. But I think the CFAA has been sufficiently reduced in scope after Van Buren v United States [0]
Hacking is not just authorised use of a system. Hacking and hacking techniques can apply to systems you fully own or systems which you are authorised to hack.
Hacking is using something in a way that the designer didn’t anticipate or intend on.
Adobe designed pdf to behave this way. Placing layers over text doesn’t remove the text from the file. They have a specific redaction feature for that purpose.
Placing a black box on the text isn’t a redaction any more than placing a sticky note would be. No reasonable person can expect a sticky note to permanently prevent readers from seeing text and no reasonable person can expect a black overlay box in pdf to prevent reading text because this is literally a fundamental feature of pdfs as a layer format file
But copying and pasting text of publicly released documents is not illegal. Accessing someone’s computer is illegal.
While maybe it could fall under the umbrella of hacking in some general way, articles, and especially titles, should be more precise.
You guessing my password is not the same as a know and expected behavior of a program. Adobe has a specific feature to redact. PDF is a format known to have layers. Lawyers are trained on day one not to make this mistake. (I am a recovering lawyer). This is either incompetence or deliberate disclosure.
It's very silly to say they "love" them. It's unlikely anyone is happy this happened. They are a news company, they report news, and people are interested most of all in bad things that have happened.
No it's not silly. These companies would be at a tiny fraction of their current revenue if people didn't like reading bad news and especially terrible tragedies. How much do you think their page views spike when there is an active manhunt or major events that happen? From a business perspective: they love them.
With OpenAI at least you can specify the cache key and they even have this in the docs:
Use the
prompt_cache_key
parameter consistently across requests that share common prefixes. Select a granularity that keeps each unique prefix-prompt_cache_key combination below 15 requests per minute to avoid cache overflow.
It would be important to use for relatively high traffic use cases
Let's say you have a chatbot with hundreds of active users, their requests could get routed to different machines which would mean the implicit caching wouldn't work
If you set the cache key to a user id then it would be more likely each user's chat could get cached on subsequent requests
> you'll have a better shot at dragging an actual person in front of a judge than for 99% of the other crap that's on the chrome web store
Based on what? The same instinct that told you having an address and phone number makes an entity legitimate? The chance the people behind this company live in the US is incredibly low. And even if they do live in the US what exactly would they be getting charged with and who would care enough to charge them?
And with Workers they're accessible from hundreds of locations around the world so you can get this sort of speed from almost anywhere.
reply