On Sun, Mar 17, 2013 at 1:03 AM, Brad Jorsch bjor...@wikimedia.org wrote:
This is also a captcha we're talking about. Its primary purpose is to
prevent non-human interaction.
I know, but think about it this way: why would an API need to login using
CAPTCHA? Because it's going to render that
On Mar 18, 2013 12:52 AM, Tyler Romeo tylerro...@gmail.com wrote:
If we return just an HTML blob, then we are enforcing that the client
application show the user exactly that output. If we output
machine-readable information, then the client can render the CAPTCHA
however it wants.
Which is
On Thu, 14 Mar 2013 12:55:16 -0700, Brion Vibber bvib...@wikimedia.org
wrote:
Text captchas will have a 'question' subfield to be presented; image
captchas will have a 'url' field which should be loaded as the image.
'type' and 'mime' will vary, and probably shouldn't be used too closely.
On Sat, Mar 16, 2013 at 2:47 AM, Daniel Friesen
dan...@nadir-seen-fire.comwrote:
On Thu, 14 Mar 2013 12:55:16 -0700, Brion Vibber bvib...@wikimedia.org
wrote:
Text captchas will have a 'question' subfield to be presented; image
captchas will have a 'url' field which should be loaded as the
On Sat, Mar 16, 2013 at 11:19 AM, Brad Jorsch bjor...@wikimedia.org wrote:
so an implementation of
KittenAuth could return a blob of HTML
This is the API we're talking about. It's primary purpose is to allow
machine-parse-able interaction. It's probably not the best idea to return
pure HTML
On Sat, Mar 16, 2013 at 10:48 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Sat, Mar 16, 2013 at 11:19 AM, Brad Jorsch bjor...@wikimedia.org
wrote:
so an implementation of
KittenAuth could return a blob of HTML
This is the API we're talking about. It's primary purpose is to allow
