A major bug made it into the June 9 web release. If you foxgloved an image, downloaded it, and re-uploaded it to Verify, you could get "No message found." That should never happen, and it's fixed.
Fixed
"No message found" on freshly foxgloved images. Two causes. First, the v1.1 selective encoder was so strict about avoiding visible artifacts that most real artwork didn't have enough textured regions to carry the message at all — and the embed was skipped. Second, on very dark or very bright flat regions, the smooth block-edge blending couldn't push pixel values past pure black or pure white, so some embedded bits read back flipped.
Older foxgloved images read as "no message." The June 9 update changed how the decoder picks which parts of the image to read, which silently broke verification for every image poisoned with earlier versions. The decoder now also reads the original layout, so your existing protected images verify again.
A long message plus artist credit could never embed. The hidden message can carry 124 characters total, but the message box allowed 280 — and your artist credit is appended on top of that. With a name and handle filled in, even the default message exceeded what any image can physically hold, so embedding failed on every image, in every mode. The message is now trimmed to fit (your artist credit is never cut), and the character counter shows the real remaining budget live as you type or fill in your credit.
Changed
- The embed is now verified before you get it. Foxglove decodes the message back from the actual pixels before saying it embedded. If the clean textured-only embed wouldn't survive, it progressively allows flatter regions until the message reads back perfectly. If Foxglove says the message is in there, it's in there.
- Visible signature is applied before the hidden message, so adding your signature can no longer overwrite parts of the message.
The trade-off, updated: v1.1 chose "no visible artifacts" over "message always embeds," and silently skipped flat images. That was the wrong balance — the message is the point. Now the clean embed is tried first, and only if your image can't carry it invisibly does Foxglove fall back to embedding in flatter regions (where you might see very faint shifts, mostly in dark areas). The notice on the results screen still tells you what happened.