pippin wrote: > OK. It should usually only take a few seconds or minutes but e-mails > sometimes have relay delays. > > > Well, "all at ickstream" currently isn't too many :) Those who have > admin access to the server can see the mail address you used to create > the ickStream account, not the account details for connected services. > > Whether we have your passwords or not in the database depends on the > service (other than with Logitech, BTW, which always connects using your > account information IIRC, at least I don't remember ever seeing any > oAuth on MySB). Wherever an oAuth authentication is available, we use > it. oAuth will not give us the full account information but just the > user ID and an authentication handle which then can only be used by > ickStream and which you can usually revoke on the service at any time > even without ickStream involvement. This is for example what SoundCloud > does. > This is also how the login providers we use work. If you login with, > say, facebook, we don't get your facebook password but just an e-mail > address and the confirmation from facebook that you are correctly logged > in through their account. > > Others like TIDAL or Qobuz don't use this yet and there we do have to > store both username and password to get access. > > > > Good to hear that, have fun! > > Regarding your earlier question on devices, let me answer although you > now removed the question. We don't get any details data from your > players, what we store is the player identity. This means: the player > name, the MAC and the UUID the player has created. That's how the > players are identified in our system. > The idea behind ickStream is to be licensed to vendors and we have to > make sure that the beta is not being used commercially, we would not be > allowed to do that for all the services provided under the terms of the > open beta, vendors will have to use a commercial license for that which > has other terms (but then they could also get more services...)
Thanks for the detailed answers, appreciated. Typical the too I use and they both need open passwords, ho hum :) I have no issue by the way, I just like to know what data is exposed and what is not. I'd prefer those details to be encrypted of course, but its clearly not in your interests to use this data with all the work you have put into ickstream so far. Again no offence meant or implied. Ok thanks for answering the question I removed. I assumed the data for the device was required for me to use your services so later felt it was not so much an issue, which is why I removed it. Certainly now you have explained it, it seems its the minimum information you need to identify the deice and allow me to use the service. Again, thanks for the teams efforts and opening it up to users as a plugin. ------------------------------------------------------------------------ local.bin's Profile: http://forums.slimdevices.com/member.php?userid=22053 View this thread: http://forums.slimdevices.com/showthread.php?t=102497 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
