I don't think that would make it less useful; either the bot reads it right or it doesn't, the leeway introduced by allowing any order input is miniscule, I think. So I updated it so it won't get fussy about order.
Hi everybody, designer here. I really appreciate all the feedback; this concept is still in its infancy and can obviously use quite a bit of improvement, but I'm trying to tweak it as best I can to maximize its usability.
Couple of notes:
1. The ultimate intention is to either pull images (both satellite and decoy) from the web as they are needed or create a database of images and update it regularly. Thus identifying images as real or decoy will only work on a short-term basis; there will always be new images entering the fold.
2. If people like this concept well enough to keep at it, I'm planning to automate some kind of color-matching scheme so that it's not possible to just look at the histograms of the images and identify the satellite images thusly.
3. I'm only just starting to learn about OCR, so at this moment I have no idea whether it's worth bothering to disguise letters or even whether it's worth using letters at all. I prefer having a two-tiered approach; having to ID a satellite image AND identify characters. If the bots are too good at identifying the characters and/or it's too hard for humans, that just leaves the satellite question and from what I've read that's not a high enough level of entropy.
4. I don't have anything lined up for an audio solution just yet. I'm fooling around with a few concepts, but nothing worth mentioning just yet.
5. Thanks to all those who wrote in suggestions/solutions and signed up!
In theory, there are lots of options for skins - fully visible/opaque, completely invisible (with some sort of icon to let you know it's active), any range of transparent, animated effects like heat haze, water ripple, etc. Kind of fun to think about, actually.
I was working on the versions for Colemak and Dvorak users at the same time and forgot to update the original; it's sorted now. Please give it another try!
Depends on whether your keyboard is mapped to the Dvorak layout or Qwerty (basically, try one, if it doesn't work the way it's supposed to, use the other one)
Sorry about that - I was working on the CHORDMAK (Colemak-based) version at the same time and forgot to fix it. It's sorted now - thanks for the heads up!