To give some more context: I tried updating my status from a Java app, not from a browser. I managed to write the utterly trivial code to update my status using HTTP 'Basic' and then figured that using OAuth as a direct replacement for HTTP 'Basic' might work. Unfortunately it didn't. I would like to it; since sending an HMAC of a nonce, a timestamp and my password would make me happier than sending my password in the clear in the style of HTTP 'Basic'.
So the rephrased question is: Do twitter support "OAuth as a direct replacement of HTTP 'Basic'"? If so I obviously got my HMAC computation wrong or used a bad timestamp or am not allowed to use OAuth. If OAuth cannot be used in place of HTTP 'Basic' at twitter, my question is: why not? I accept that browsers might not support OAuth (yet) but, e.g., mobile phone twitter clients could easily. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
