Block a user
Handling JWT secret key secrecy
We need lots of non-public images
For now, I will simply have three images that look really good for marketability purposes lol. Should look serious and cool. Have a lot of deep symbolism.
We need a unique UUID to give the client to associate with CAPTCHAs
User shouldn't be able to see "n" (number of spins)
The symmetric encryption to store the solution in the JWT...kinda sucks
How many images to provide per challenge?
Integrate new CAPTCHA generation code into current webapp
I'm going to try to make it work without setting up the JWT stuff or worrying about recursive Jinja complications. I'll just generate the html and serve it and use my current cookie concoction.
Integrate new CAPTCHA generation code into current webapp
This is probably the most important issue because without this, there isn't even a working MVP
Integrate new CAPTCHA generation code into current webapp
I will be editing these issues to flesh them out, the above is a rough draft still...
Integrate new CAPTCHA generation code into current webapp
Images are cut off at edges when rotated
Rotated images sometimes look grainy and unnatural, making it easy to eliminate certain incorrect options
Move this repo to a different platform
We need lots of non-public images