Not only was this made with an LLM, it breaks so many other things but If you use this font to protect your text from AI, it also blocks *me, a human* because I use a screen reader.
-
There's a tiiiiny little problem with "quit trying": I can't afford to. Without defenses up, a €46/month VPS (4 CPUs, 8GiB RAM) died under the crawler assault in about 2 minutes.
It's not that what I was serving was inefficient... it never got to serving! It died while trying to keep up with TLS handshakes at over 10 thousand requests / second. Yes, that was sustained over multiple days. I temporarily scaled up to 16 cores, and that still died.
For comparison, I currently pay €8/month for my VPS. There is no proof of work, no JavaScript required, no silly fonts. I've been using the same measures for about a year now, the bots have not adapted (and if they do, I have a dozen other tricks up my sleeve, none of which affects the legit visitor any more than the current measures do).
I can afford €8/month. I cannot afford €45+. They can very easily DDoS me if I let my guards down, yet, I can't scale up infinitely.
So defense it is. There are reasonable defenses that work.
@algernon @alice Yeah you have a point. I hate this timeline so much! What about https://rollenspiel.social/@ArneBab/117032564006229790
-
Not only was this made with an LLM, it breaks so many other things but If you use this font to protect your text from AI, it also blocks *me, a human* because I use a screen reader. I did try the demo. If you want me to remove your RSS feed, this is the best font to prevent blind people from reading your blog/words. That timer is an inaccessible solution. https://shieldfont.org/#hero #AI #LLM #Accessibility #A11y
@WeirdWriter
But the page says:Screen readers get the real words.
ShieldFont hides scrambled passages from accessibility tools by default with aria-hidden="true".
The real words ship sealed in the same page, and the reader’s own browser uncovers them by solving a compute-heavy puzzle — a few seconds of their CPU, and a cost a bulk scraper would rather not pay. It needs JavaScript, the reader waits while everyone else does not, and a shielded block still
-
@WeirdWriter
But the page says:Screen readers get the real words.
ShieldFont hides scrambled passages from accessibility tools by default with aria-hidden="true".
The real words ship sealed in the same page, and the reader’s own browser uncovers them by solving a compute-heavy puzzle — a few seconds of their CPU, and a cost a bulk scraper would rather not pay. It needs JavaScript, the reader waits while everyone else does not, and a shielded block still
fails WCAG 2.2 SC 1.3.1. This makes a shielded page humane. It does not make it compliant, and we will not say otherwise.
@WeirdWriter -
@ArneBab @jpaskaruk @WeirdWriter If the decoy text amounts to an unvarying word substitution cipher, any AI model seeing enough cases of it should be able to trivially solve it.
If for any reason that fails, AI owners who also own captcha farms will be able to have humans working for pennies display the text on a splitscreen, one with JS enabled and one not so as to show both texts at once. They can then list what decoy words go with what real ones and feed that back to the AI.
@ArneBab @jpaskaruk @WeirdWriter In general fixed substitution ciphers are extremely weak. If this was applied to a single word as a captcha, I doubt it could resist being solved by a cheap, bottom of the barrel Android phone CPU.
-
@alice Yup. I honestly wish everybody would just quit trying because everything anybody does that tries to prevent LLMs has made everything bloated, a far worse user experience, and will prevent LLMs from scraping will inevitably fuck up those that don’t use JavaScript, or maybe have a custom font, or anything else and besides, every single one of these preventative measures can be circumvented
@WeirdWriter @alice I think things like this are probably a "just stop trying", but, things like trying to stop scrapers is, at this point, mandatory for a lot of smaller sites/hosts, just... due to bandwidth limits and cost, I think.
The best solution would be to prevent it through social or legal changes - as in, not a technical solution to the problem at all. There is some political pressure in that direction, but, a lot of money pushing back, so, hard to tell where that lands currently. -
@WeirdWriter it plain doesn't work with uBO lmao
@WeirdWriter@caneandable.social @hyphen@duwa.ng
this concert is already copped
couldn't have said it better myself -
Not only was this made with an LLM, it breaks so many other things but If you use this font to protect your text from AI, it also blocks *me, a human* because I use a screen reader. I did try the demo. If you want me to remove your RSS feed, this is the best font to prevent blind people from reading your blog/words. That timer is an inaccessible solution. https://shieldfont.org/#hero #AI #LLM #Accessibility #A11y
@WeirdWriter@caneandable.social Even as a sighted person, I couldn't read that page without JavaScript so... cool /s.
-
@algernon @alice Yeah you have a point. I hate this timeline so much! What about https://rollenspiel.social/@ArneBab/117032564006229790
@WeirdWriter My website couldn't be simpler (it's all static, neatly fits into memory). Server dies before it even has a chance to serve it - during TLS handshake. Can't make that much more efficient.
Granted, I host a... few handful of sites on that €8 VPS. But the content isn't the problem, the crazy request rate is, and that is outside of my control.
(Hence part of my defense is firewalling crawlers off. Can't TLS handshake if packets are dropped! Problem solved.)
-
Not only was this made with an LLM, it breaks so many other things but If you use this font to protect your text from AI, it also blocks *me, a human* because I use a screen reader. I did try the demo. If you want me to remove your RSS feed, this is the best font to prevent blind people from reading your blog/words. That timer is an inaccessible solution. https://shieldfont.org/#hero #AI #LLM #Accessibility #A11y
@WeirdWriter This is wild because they make a specific claim that screen readers get the real, unaltered text. I wonder how much testing they performed, and with how many different screen readers
-
@WeirdWriter @leeloo thanks both.
-
A abekonge@venner.network shared this topic
-
Not only was this made with an LLM, it breaks so many other things but If you use this font to protect your text from AI, it also blocks *me, a human* because I use a screen reader. I did try the demo. If you want me to remove your RSS feed, this is the best font to prevent blind people from reading your blog/words. That timer is an inaccessible solution. https://shieldfont.org/#hero #AI #LLM #Accessibility #A11y
@WeirdWriter it specifically says that is works with screen readers so that's really frustrating. I love the intent of the project but if it's not accessible it's not a good product. Period.
-
P pelle@veganism.social shared this topic
