Not 100% sure what you are suggesting. Are you suggesting for the
authorization step that instead of directing the user to twitter
instead receive a captcha image which the user inputs that # and we
send back to get the access token?
I am not sure that is such a good idea, mainly because captchas
On 1/22/2010 7:48 AM, Josh Roesslein wrote:
Not 100% sure what you are suggesting. Are you suggesting for the
authorization step that instead of directing the user to twitter
instead receive a captcha image which the user inputs that # and we
send back to get the access token?
I am not sure that
How does Twitter verify which user is completing the CAPTCHA?
Abraham
On Fri, Jan 22, 2010 at 07:06, John Meyer john.l.me...@gmail.com wrote:
On 1/22/2010 7:48 AM, Josh Roesslein wrote:
Not 100% sure what you are suggesting. Are you suggesting for the
authorization step that instead of
Good question. I'm not saying that this is the best idea out there, but
if desktop (and third party non web apps) developers have problems I
tihnk we should at least start entertaining some suggestions. Some may
pan out better than others, but at least get the ideas out there.
On 1/22/2010
