Le mardi 12 mai 2009 à 17:50 +0100, Peter a écrit : > On Tue, May 12, 2009 at 5:45 PM, Gilles Dartiguelongue > <gilles dartiguelongue esiee org> wrote: > > > > Le mardi 28 avril 2009 à 09:46 +0100, Peter a écrit : > >> On Tue, Apr 28, 2009 at 2:17 AM, Jonathan Matthew <jonathan d14n org> wrote: > > [snip] > >> That sounds like what Last.fm expect you to do: > >> http://www.last.fm/api/authspec > >> > >> i.e. This password prompt in a browser is a one off operation, so > >> embedding a browser in RB just for this is overkill. KISS? > >> > >> Once validated, there is a one hour window to use the token, and if > >> done, the registration is indefinite. However, you would need to test > >> the case where the use logs into their last.fm account to revoke RB's > >> access. > >> > >> You could also try and use the "Authentication For Mobile > >> Applications" which looks much more straight forward as you can > >> directly supply an md5 of their username and password. Of course, > >> last.fm don't want desktop applications to do this. > > > > now this is ugly, why provide an API for integration if you need extra > > apps to get where the user wants. I would personally hate starting a web > > browser just to do that (yes I often close it). > > > > Did you mean to send this to just me? I agree with you: Last.fm forcing > applications to launch a web browser is a bit nasty - but it is only required > once to validate the username/password. > > Peter No I wanted to send it to the list but failed it seems :) Even if the thing is a one time activation, I'd need to run it on at least 3 machines, home, work, laptop while I already have my account registered on those machines. Extra steps kill the fun, it would probably be easier to migrate to another service (speaking for myself here). -- Gilles Dartiguelongue <gilles dartiguelongue esiee org>
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=