That's not an unsolvable problem. Checking visibility is easy, computer graphics have been doing this since forever. Fonts that are too small, ditto. Contrast is well understood.
If you do want to render, you don't have to do the convoluted PDF route. That's what the user would do, the software would just use its normal drawing code. OCR is neither needed nor desirable. OCR errors would erroneously flag perfectly normal text, and it can be fooled just like a human can. You can detect whether or not there's any rendering with the bounding box of whatever text section you are looking for (something Word already has to calculate if it wants to render correctly on screen).
I'm only talking about checking for visible text. This will not solve the larger problem of malicious AI instructions.
Embed text in an image, a human will read it just fine. Perfectly visible but opaque to AI. It'd be obnoxious to turn it into an attack, but you can replace letters with images in phrases so that humans read "she believed" while AI reads "he lied."
Just like every AI cycle that came before. At every cycle, we get a new tool. But we also get an extended "AI Winter" where investment dries up. This has been happening since the 1980s, we just keep redefining what "AI" is. At every cycle we move the line a bit; at one point voice recognition was firmly in the AI camp(and before that, science fiction). Now we have a machine that can do that in our pockets and nobody cares.
Douglas Hofstadter talked about these moving goalposts for AI in his book Gödel, Escher, Bach. I remember when a program that could win at chess was considered impossibly strong AI. Then, the game go. Etc.
Heinlein in his book The Moon Is A Harsh Mistress imagined that people in the future would find it worthwhile, even necessary, to learn an artifical language LogLan so they could talk with computers. LogLan (Logical Language) would be designed to be totally unambiguous, a necessity for speaking with a computer. He didn't imagine that we'd simply throw so much compute at the problem that we'd teach computers to understand our vague, mumbled natural languages in all their diversity.
a friend of mine did a high school project where he and a friend learnt it well enough to have a short conversation with each other. That's the only time it has come up in life until now. I hope he sees this.
Even for Brazil, even for the most dangerous cities, that's still an insane number of kidnappings. They happen enough that you need to be aware and be careful to not be an easy target, but it's still a rare event overall.
> It says so much about how our society treats the neurodivergent that it's considered a non-extreme opinion that a dead child is preferable to an autistic one.
They did not set out to kill the child. And the autism wasn't even the biggest issue. The issue is the developmental delays that were expected to compound the more the brain was left untreated.
If you are on AWS, the direct attached storage option you have is ephemeral volumes. That's bad. If the hypervisor fails you lose data. Which is fine, you have replicas. If there's an event that takes out multiple machines at once, even for a moment, you are hosed(this can be AWS issues, or could be as simple as automation misbehaving and shutting machines down).
I'm all for treating DB as cattle, but your cattle needs to be able to survive long enough.
EBS is expensive but it works for PG. AWS uses EBS for RDS databases. Calling that a 'mistake' is a tall order.
If it works for you it’s great but the RDS EBS limitations are real enough… AWS built Aurora and for RDS a new 3 node topology using local SSDs for writes and EBS only for the data directly.
reply