jtfields;133034 Wrote: > I don't know what kind of demand there would be for this type of > functionality. Most people probably want most of their players to have > access to their entire collection so demand very well might be low. I > would guess it would mostly be used in situations where you wanted > parental control, in households where musical tastes varied widely > (i.e. Dad could care less about his Squeezebox having kid's Britney > Spears and kid doesn't want Dad's Frank Sinatra, etc.), or if you had a > Squeezebox in a location where you wanted a limited library. That said, > I'm the first to admit that the suggestion is a selfish one. ;) There's a _lot_ of call for this type of functionality. As I pointed out in a reply above, this really requires user management of some kind, coupled with the concept of a player belonging to a given user, plus multiple libraries and/or filtering.
Keep in mind that you not only have to lock down the player through the remote ui, but you need to control what can be seen and played through the web ui. That requires knowing who's logged in to the web interface and then being able to control what music they see. Many people just want to be able to browse their own music without having to wade through the music of their children, or their husband, etc. It's less of a content-security concern, but essentially the same thing. There's also the 'Christmas party' or 'kids party' scenarios. You have a player that you want your guests to have access to, but you need to limit what music they can play. This has all been requested and discussed quite a few times. The demand is very high. -- JJZolx Jim ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=26874 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
