Hacker News Reader

Comment by billtarbell | Hacker News Reader

Everyone rushing to make their content AI-friendly made me want to figure out how to make content AI-unfriendly. Basically human-written words meant for human eyes only.

So I built "SoulsOnly.ttf": a font for humans not AI, and keyboard firmware to type in it.

The implementation of a font can be "hacked" to make what looks like gobbledegook to a computer, render as legible to humans. Copying and pasting text written in the font into AI to summarize is almost impossible. And to avoid AI image analysis, a version of the font can be loaded with the glyphs scattered and require a simple "focus" interaction by the reader to begin reading. Note that a sufficiently prompted AI agent can definitely read this, so it's not meant to be cryptographically sound, more just unfriendly to the common AI reader!

View on HN

Break search and screw over your disabled readers with this one weird trick! Legal in multiple countries

Point taken. This really isn't intended for that, more a fun exploration of the difference between human and AI perception. That being said, I updated the project with an analogous audio version.

I love this! But won't the machine easily pick up on this?

As they said in the comment you replied to: "Note that a sufficiently prompted AI agent can definitely read this, so it's not meant to be cryptographically sound, more just unfriendly to the common AI reader!"

It's actually not really easy for AI, without the agent doing some actual coding itself to reverse engineer the font file, or to take screenshots at different variable font intervals to zone in on the "focused" version of the variable font. All of that being said, the intention (beyond just having fun creating it) was to make it AI "unfriendly" so AI bots doing broad quick reads of it are going to be left with gobbledegook encoded characters.

Most llms can equally engage with text in picture form as text in token form. In fact my initial research on this (later corroborated by actual published papers) indicate that this is a cheap way to save on tokens.

Oh interesting and good to know on the token savings with this technique. My test with claude had it use vision and then programmatically test different variable font input variables (mimicking the user scrub interaction) until it was able to OCR it.

I mean I can't know for sure but I'm pretty sure that by the time the upper layers of the network are reached the lower level networks have already transformed the image tiles into proper position encoded embeddings of the tokens in the words in the image.

That would be my operating assumption at least.

The encoded data and the font file go over the network. The font file is executed locally on the readers machine.

My point is you can just render the file and send to AI...

Hilarious. Nice work

Thanks! Font against the machine! lol

lol

Fuck blind people I guess?

I don't know why you'd feel so hostile towards the blind, but you do you...

They meant that this is a technique that relies on a person's vision, which means that the blind, by definition, are being excluded. They weren't being hostile toward the blind, they were pointing out that the project itself is hostile towards the blind.

Certainly no. But point taken. This really isn't intended for use on a website like that, more a fun exploration of the difference between human and AI perception. That being said, I updated the project with an analogous audio experiment version for the unsighted.

Reply on news.ycombinator.com