There's a very bad canvas bug in Android Chrome on some devices that's making the original show through - you're supposed to be painting on white (been looking for a workaround & it's fixed in Chrome Canary)
There's a bug in Android Chrome with certain devices that thoroughly breaks some canvas operations, you're not supposed to be painting over the original. Been looking for workarounds but so far only managed to make it glitch in different ways (apparently it's fixed in Chrome Canary)
It's just simple HTML/CSS/JS and canvas manipulation; scoring is done using 'difference' compositing & checking pixel RGB values, and brushes are built up from bog-standard canvas strokes.
All client-side; would've been nice to store & play back the drawing process, but that would've been a lot of extra work and created a whole load more UI/design/clutter problems to solve (it was very much a keep-it-small-and-get-it-launched project, around 2.75 days total).
Would've been nice to do that (& maybe play back the drawing process), but I was keen to keep the project small & get it launched (took 2.75 days in total, I tweeted the dev process).
I made this game; in case anyone's wondering how the scoring works:
It draws your version over the original with 'difference' compositing, then downscales the result (using 'medium' quality to avoid most pixels getting skipped) and adds up the R, G & B values for every pixel in that small image. This total is then compared with the total difference for the initial state (which represents 0%).
Darker areas have the biggest initial difference, and the whole pic is darker than the initial canvas, so get a lot of paint down and pay most attention to the dark bits, you'll soon get over 70%. 85% is v good, and I think 90% is probably possible with enough skill and speed.
I wouldn't be surprised if it doesn't cover that, I can imagine it'd be tricky to include without adding tens of bytes (10-20 bytes could be freed up by using slightly hackier function calls to/from the display, so perhaps Óscar will add more features/intelligence one day)
It looks 4 steps ahead with a points system for pieces & positions, but has no sense of broader strategy.
(The original code looked ahead 3 moves, but browsers & devices have improved a lot in the last 11 years)
Hi, I made the quiz and tried to design it to make judging by appearance work as poorly as possible, so the initial daft premise then becomes something a little bit more interesting as you get some wrong.
But I think it's reasonable to be wary of the issue, particularly with endless problems emerging nowadays with facial recognition tech.
Those saying you're taking this too seriously are wrong - the project is a joke, but the issues you highlight aren't.
I made the font, and if it was a serious attempt at a moderation tool or trying to comprehensively cover 'bad words' then such slurs would certainly be included. But it's VERY limited in scope, there's just enough for the joke to work (core 4-letter words plus a set of words people grumbled were missing) and it's focused around what most people would consider to be everyday swearing (rather than discriminatory or highly contextual terms). I also felt that adding slurs to such a limited word list would risk highlighting them & encouraging their use to make 'funny' screenshots etc
Please keep questioning these things, I'm well aware that even silly projects can raise serious issues and try to give them enough thought.