A PNG file can now say how it was made, in a text chunk keyed `qr-made` that a code generator writes. Your browser reads it and checks every claim it can against the reading; one mismatch, and the whole record is ignored, with one line saying why. A file whose own details check out is marked as the original graphic by itself, and the page gives the picture's own width, explains its art in words and compares the squares meant with the squares zxing-cpp read; every number still comes from the reading. The record is removed before the picture is sent, so the server's answer is the same with or without it.
The README explains this beside the code's facts as made. Its Privacy section now says that if a file says how it was made, your browser reads that and removes it before the picture is sent; that anything else a file carries is sent with it and deleted unread, a photo's location among them; and that the page marks a file whose details check out by itself, which starts a design test that…
A picture marked as the original graphic is now tested as a design, by itself: the page sends it again, and this server scans it beside a plain code with the same content in 20 simulated everyday scenes, at the width worked out for it. The answer says whether the scanners it names read the design as well as a plain code or worse, or that the test couldn't tell, with a next step, and "How this was tested" behind "+". In Google Chrome on a Mac, or on an Android phone with Google Play, Apple's or Google's scanner can join the test in your own browser: by itself until it has done so in 3 of a page's tests, then with one tap.
The README gains "Testing a design": how the test works, how it judges each scanner, when your browser's scanner joins, and its limits. Its Privacy section now says that marking a picture as the original graphic sends it again, and what your browser fetches for the test. The page's own notes on how pictures are placed say the same.
Co-Authored-By: Claude Opus 5.5 <no…
3 days ago
Facts from each code at its own size; the design test's server, not yet on the page
- Where zxing-cpp read a content more than once in a frame, the facts and checks leave out its reads from its own smaller copies of that frame (README, /api/measure).
- The design test's server (/api/design) is added and starts with the Space; the page doesn't offer it yet.
- Chrome on Android leaves its own scanner out of a test whose raw bytes aren't UTF-8 text.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HykRoFZnnb98KRf6Xxomka