Very interesting video if you scroll down their page a short distance.
Please, no, let’s not do this.
Even if it wasn’t made by Claude, take a moment to think about what this does to blind users and other users who rely on screen readers who disable JavaScript for whatever reason (and there are legitimate reasons).
Besides, this technique is not novel. Amazon does it to scramble their ebooks, and a random guy broke it in a couple weekends. Considering AI bros are already breaking Anubis, it’s not a stretch to say they’d break this in no time flat.
Like every other DRM scheme on Earth, it harms legitimate users while doing nothing to stop the people it’s supposed to stop.
Their site says they’re friendly to screen readers, but we’ve got to do SOMETHING, yes?
Yeah, legislature that bans AI bots, for starters
101% with you.
Anything a screenreader can use a bot can use. Killing bots via text kills screen readers necessarily, no? How do you know a bot isnt using screen reader tech?
Here’s what they say about it.
Worth noting that the linked GitHub repo is full of commits from Claude
I was hopeful until I saw that and ironically instructions for LLM Agents to follow. I won’t be touching that with an 80 foot pole. The irony, is honestly darkly humorous.
I mean… Github
But still, yucky
I don’t know if this is this is the same font that was going around before buy accessibility advocates quickly flagged it didn’t work with screen readers. Logically if a screenreader can read to a human, a scrapper would be able to read it. So this approach is probably a non starter.
I’ve seen lots of objection to this font from accessibility advocates…if you go to the website, however, it seems like they’ve accounted for screenreaders. It seems like a lot of people go straight to shouting down this technology without looking into it. That said, I have no idea how this tech works, how screen readers work, or whether these two things are compatible, just saying maybe read their webpage before getting all up in arms.
The advocates im referencing use screen readers and were unable to use sites with it. maybe this is a different solution that can some how account for that.
I still don’t see how a scrapper wouldn’t just use the same screen reader content as their input though. If a machine can read the content, why would we expect another machine not to read the content?
It’s said in the screenshot. To get the screen reader-accessible text, you need to press a specific button (instructions are displayed before the scrambled text), and then your browser will be computing some complicated puzzle for a few seconds in order to “unscramble” the text
This puzzle is computationally expensive, so while it doesn’t fully protect against bots, it drives the cost of scraping way up. And since this scraping is done to somehow profit from it, driving the cost up is definitely a deterrent
Hey you with a special tool to overcome difficulties, we fucked your tool and now there’s an extra step for you.
You didn’t even say thank you.
What if you have a plug in that make the font more readable. I.e. change all text dislexic friendly fonts. I guess you can turn it off but your then asking users to turn off features they find useful.
It’s a complete non-starter, yes. The screen reader problem is real
If the screen reader then needs to read the pixels of the screen then you need to increase the resources required and then build an AI to read text oh no it’s happening again!
I saw headlines about this before and ignored it, but actually reading the page this time I see that it’s much more sophisticated than I expected, especially the part about having a mechanism to locally unlock for accessibility with a compute cost.
