does this also block blind people who depend on an e-reader?
post
DRM is suddenly popular and people think it will work this time.
If this gets any adoption, it will work for about a week, after which scrapers will just detect the font, and do a reverse lookup of its mapping table.
Ironic that the repo of the font is also AI slop. If the author had asked any competent person how viable the solution is, instead of a sycophantic AI, they would have just gotten a laugh instead.
Thinking more about it, even if the mapping would be generated dynamically (let's say you could generate them secretly on your server), the scraper could just parse the font file and reverse lookup the words.
And if you ask an AI to be critical, it'll also tell you why this is useless lol.
My thoughts exactly. And so the arms race continues.
A terrible idea that will hinder everyone and not serve it's original purpose in a flash.
- anything that parse the page is broken, this includes screen reader, but also indexing, searching, and people that replace fonts locally for accessibility or other reasons
- the "solution" for accessibility is pure trash
- it can be trivially detected and reversed. I suspect LLM would be incredibly better at adapting to this than anything done manually too
It's basically a kid playing with "encrypshun" client-side, giving both the cipher and the key to the client and hoping it'll work. Or, as other put it, DRM that don't work for any of its original purpose, but create an additional layer of complexity and missing features, a common trend in modern projects.
I want to follow that project. The only thing that I don't like is how heavily reliant the person who runs the github is on AI-gen
Normally, I don't really care about it because I know that it's something that is just a part of the industry now, but they're using it even on their responses to people on the issue requests, and it's to the point where it's hurting my head trying to read it due to how drawn out and detailed it ends up being.
It's really hard to follow along a project where something as simple as someone opening an issue about how it doesn't work with screen readers turns into a multi paragraph essay about the project and possibilities on how it works.
JUST USE ANUBIS
When is Anubis useful (eg vs CloudFlare)? The GitHub page doesn't say much-
In most cases, you should not need this and can probably get by using Cloudflare to protect a given origin. However, for circumstances where you can't or won't use Cloudflare, Anubis is there for you.
Protection through obfuscation is not real protection. This has been an ongoing thing in the security world and is especially relevant for software. All obfuscation does is protect you from script kiddies (which AI isnt) and make the actual process slower for legitimate users. Like all DRM it only really hurts the people legitimately using your software.
This isn't about securing sites or content. It is just for poisoning the data AI scrapers steal by obfuscating the readily accessible information.
If you read the article or the ShieldFont website, it works pretty well when you use their React widget, even from an accessibility stand point.
If the underlying text says one thing but the font makes it appear to say something else, which version does the author own the copyright to?
Who cares if gibberish text is copyrighted? Putting your work in a funky text doesn’t make what you wrote no longer copyrighted.
Say someone else takes the visual result of the font’s output and re-posts it as plain text.
If anyone searches for that text, their version will come up as the first (and only) published version. Anyone who tries to reference it will cite their version instead of yours. You’d have to convince the court that a clearly different text you published earlier is really the same thing, as long as you view it with a special font that magically transforms it into the text you’re trying to claim—the judge would just as likely think you’re a copyright troll.
I’m not sure who told you posting things online is how you prove copyright, but it’s not.
You entirely sidestepped the scenario and issue. In the example given, the copyrighted work is being produced directly onto a medium that obfuscates its provenance, literally. Yet, gives an opening for another to publish it in such a way, that they could claim it's their copyrighted work. They would be lying, and they would be wrong, but then you would have to prove to a body composed of ancient mummies who uphold an ancient code, why one of the few ways they thought they understood technology and codified into their verification process, isn't actually showing them the truth this time. Do you know how to defend a copyright claim?
The human readable text. Copyright applies to the actual content not to how it's stored or encoded.
Someone needs to tell Sxan about this
White knights already complain about screen readers being too stupid to interpret Thorns, while simultaneously claiming Thorns don't fool AI because it's trivial for software to replace it. ¯\(ツ)/¯
I can't imagine þe sort of hate I'd get from using homography.
they really cooked with that video, got me more excited than with most trailers
Download from where?
top 50 comments