> why not focus the efforts on coming up with [...] workable solutions As I understood your specification says: 1) new users should be forced to run the latest stable FW on their controller, there shouldn't be a way to work around this. 2) it isn't mandatory for users to have a SN-account to achieve that (though your current method works this way).
>From these specs follows a third mandatory spec: 3) new shippings of the controller can't contain an installation CD with a probably dated SqueezeServer-version. If you had such shipping, the controller would be upgraded through SN upon first start, and than be downgraded by the dated SqueezeServer from the CD. The user would be in an inifinite loop of up- and downgrades. I conclude, that the SqueezeServer will have to be downloaded 'fresh' by new users as well. If you ship a CD it will 'just' have a small application that will guide through the process of downloading. If 1+3 hold true, we are in a very comfortable situation: - On first boot the controller just has to look for a local SqueezeServer. If it finds one it can be sure, that this must be a 'fresh' downloaded one with the latest firmware that was available at the time of buying. - If it isn't finding a SqueezeServer (because the user didn't install one yet), it is forcing the user to open a SN-account, to give the user instant access to the latest firmware and internet-radio. Actually you are able to solve all of your problems: - new unaware users, who just turn on their new gadget, have a great first time experience, given that they have a very good internet connection. they are forced to open a SN-account, get the latest firmware and are really happy about all those cool radio stations they now have access to. - users with no or very low bandwidth have a very simple workaround: just donwload and install a new squeezeserver on the local network - then still have a lot of fun with local music (these type of 'low-bandwidth'-users isn't helped with a SN-account and internet-radio anyway) - people doing a lot of factory resets (beta-testers, developers) are happy as well: they are not forced to always enter their full account details (this made me going nuts with a long email-adress + long password), because they have a SqueezeServer running as well. SN-account-details are saved in the server settings - so they have the goods of both worlds: SN-access + local-music. Please give me hints on where I made mistakes in my thinking. I can only think that if point 2) doesn't hold true, you will have to stay with your current implementation, because thats the only one that forces users to have a SN-account. -- bluegaspode ------------------------------------------------------------------------ bluegaspode's Profile: http://forums.slimdevices.com/member.php?userid=31651 View this thread: http://forums.slimdevices.com/showthread.php?t=66898 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
