! This was it.
@ Yeah.
# Mmm k.

On Aug 14, 3:06 am, Tom van der Woerdt <i...@tvdw.eu> wrote:
> On 8/13/10 11:58 PM, Gurpartap Singh wrote:
>
>
>
>
>
> > Will talk in points:
>
> > # An existingOAuthappwhich already has xAuth access, works
> > perfectly in the implementation.
>
> > # Created a newOAuthappwith Twitter. Got xAuth access for it
> > through email.
>
> > # Replaced the implementation's API keys to the newOAuthapp'sAPI
> > keys.
>
> > # Getting 401 error onOAuthecho attempt withTwitpic.
>
> > # If the original API key is used, it works fine.
>
> > # "Use Twitter for login" is checked in newOAuthapp'ssettings.
>
> > # Requested Twitter to look if it really has access. They verified it
> > to have xAuth access.
>
> > Where's the catch?
>
> Yikes, points. I prefer numbers :-)
>
> 1. Don't use the same user keys for different consumer keys.
> 2.OAuthecho is not dependent on xAuth
> 3. If your application is a desktop application, you should not check
> "Use Twitter for login".
>
> Tom

Reply via email to