I'd love to know what data is sent, perhaps I'm over-cautious but
There's the optional prefs sync. Some of the data like player names
could be considered sensitive data ("Michael's Bedroom Radio"). But
syncing is optional.
Next up: the update check. In addition to the necessary data to provide
you with the update info string (OS, LMS version, locale), it reports
your LMS' unique identifier and the number of players connected to LMS.
https://github.com/Logitech/slimserver/blob/45c68d6547cabc857943e69ebfc621d7632069ad/Slim/Utils/Update.pm#L82
That's probably the only non strictly functional data transferred. But
it's also the most important for the reasons I mentioned before: as LMS
users/players aren't connected to mysb.com, it's still super useful to
be able to say "plus x players out there". Trust me: these numbers are
looked at in our interest. MySB would have been shut down a long time
ago didn't we know of the larger user base.
Every request comes with a custom UA string providing additional
information about your OS & platform, LMS version etc.
https://github.com/Logitech/slimserver/blob/45c68d6547cabc857943e69ebfc621d7632069ad/Slim/Utils/Misc.pm#L1242
This UA string as well as eg. what track a user requests from a music
service is being logged in regular access.log file by the frontend web
server. But lack of user identifier in those requests these couldn't
really be linked to a user, even if we wanted.
_______________________________________________
squeezenetwork mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezenetwork
