Hi,
Since you have all the passwords, could you not just log into the users
account and authorise access to your oauth based application?

Seriously though, I had a similar thing on twollo.com, I still allow the old
"Basic Auth way", for what ever reason people want to use it. You can still
easily maintain (for the near future) both versions of authentication and
users can still use both methods.  One of the many benefits of oauth is that
your access to the account from your application still works over password
changes - which your current implementation using basic auth wont.

Looking at what you have done, other than letting the user tweet what they
are listenting too you don't need any authentication, would it not be easier
to get the user to follow you, in response you send a DM to them with a url
in that contains a unique url in that they can then enter their lastFM
username in.  Because they are following you, you can still DM the stats
that you send.

Paul

2009/6/16 Simon <[email protected]>

>
> Hi. I made a mashup in the beginning of the year (before OAuth). You
> can check it out here: http://www.tweekly.fm.
>
> I really want to switch to OAuth (for the sake of security), but
> Twitter isn't exactly making it easy. I've read through some old
> threads, but couldn't precisely find what I wanted to say. Sorry, if
> its been said before.
>
> My mashup only requires the user to enter their details once. The only
> time they enter it again, is to delete it. It's an automation service.
> It sends data from last.fm to twitter.
>
> Switching to OAuth is a nightmare for both me (as a coder) and the
> user. I can't run both basic auth and OAuth for the same user (its the
> way my mashup works). So if a user wants to switch to OAuth, they have
> to delete the old basic auth details. Its unnecessary hurdles.
>
> Its been said before. All I want is an API method to use basic auth to
> get the OAuth access tokens. This way, I can easily write one script,
> to convert all my users to OAuth. No hassles for me, and no hassles
> for the users.
>

Reply via email to