this post was submitted on 01 Aug 2026
56 points (93.8% liked)

Technology

43323 readers
299 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 4 years ago
MODERATORS
 

If you don't want AI scrapers training themselves on your website, there's a new way to stop them that doesn't involve server-side blocking or praying they respect your instructions in robots.txt. A team of creatives have teamed up with a typography company to create a new type of font that’ll trick LLM scrapers into ingesting poisoned gibberish.

Dubbed ShieldFont, the open-source project almost seems like magic if you're not familiar with the ins and outs of computer fonts. Look at a web page written using a ShieldFont font and it’ll appear exactly as one would expect: All the content words (the nouns, verbs, adjectives and adverbs that give a sentence meaning) are the same as the writer originally wrote.

Inspect the raw HTML that a scraper reads from a ShieldFonted page, however, and you’ll see a sentence that’s essentially gibberish. Typing “good luck reading this, you useless robot” in the online demo version, for example, turns it into “good comfort reading this, you yellow barrier.”

The goal, as outlined in the ShieldFont white paper, is not to get a scraping bot to reject the text as garbage, but to convince it that the text on the page is unusual but sensible. A noun will never be swapped for a verb, for example, and a verb will never be swapped for an adjective: Swaps only come from the same grammatical pool.

you are viewing a single comment's thread
view the rest of the comments
[–] leigh@lemmy.blahaj.zone 25 points 15 hours ago (3 children)

Clever, but disabled people using screen readers shouldn’t be ignored or considered just collateral damage. 🙁

[–] ranandtoldthat@beehaw.org 6 points 8 hours ago

Yup. This project is cutting off the nose to spite the face. So easily worked around by any scraper, but makes the website worse for actual users. Accessibility is usability.

[–] TehPers@beehaw.org 3 points 9 hours ago

Unfortunately, any tools a screen reader can use to read the page are tools a LLM can use. Without challenge-based solutions like Anubis, I'm not sure what can really be done that isn't IP whack-a-mole.

If it comes down to losing accessibility or losing the website due to scrapers obliterating the hosting costs, then I think most website admins would rather just put a "use OCR" message at the top of their skip nav.

As much as I hate using JS for this, I wonder if there's a JS-based solution that gets the best of both worlds while killing off scraping. Serve this obfuscated trash initially, then swap it out after completing some challenge sometime after FCP.

[–] Midnitte@beehaw.org 7 points 15 hours ago (1 children)

I assume a screen reader that used OCR instead of just copying the text would work (for example, being able to read text in images)

[–] xianjam@programming.dev 16 points 13 hours ago* (last edited 13 hours ago)

Yes, but this is not typical and the experience is degraded compared to traditional screen readers. There are some that have limited OCR capabilities, but they're typically used for images without alt text or PDFs that are images.

This is a horrible idea. Accessibility is fairly complicated. Websites are difficult enough to navigate without this.