I'm playing with the Rdio web playback API (the SWF one, not the new beta one, 'cos I haven't asked for access to the new beta one yet), and all seems good; a user can use my app, explore music, play 30 second previews, and if that user is themselves logged in to Rdio, they can play whole songs and those songs playback out of that user's limit of playback time. Hooray, that's the idea.
However, I noticed something intriguing in
https://github.com/rdio/hello-web-playback/blob/master/token.js#L30. It says "
if you want to do playback as a particular user, pass --authenticate to rdio-call". Does this mean that if I request a getPlaybackToken using rdio-call and I pass --authenticate, that token will be authorised on *my* account -- that is, if a user comes to my web app and explores music, the songs will play back on *my* account, not the user's, and the playback time will be deducted from *my* playback time, not the user's? I'm not sure if that's what the sentence is meant to mean; in particular, having *tried* it, it doesn't seem to work like that, but if what I'm describing is not what is meant, then I don't think I understand at all what passing --authenticate to rdio-call getPlaybackToken is actually *meant* to do. Clarifications are welcome :-)
sil