Thanks for the feedback, and totally respect you wanting to question...As has been explained to you:I'm not entirely sure what you think can be done with a Machine ID. It is an identifier, nothing more and really pretty safe to share. Google it. Plenty of info out there.You come across as out of touch on privacy issues. I'm not really interested in your opinion on what is "safe to share." What is a good approach is to share only what's necessary and, based on what you've said so far, gathering machineID isn't necessary. So, it's good privacy practice to question your practice of gathering unnecessary information.A machine ID is personal data, so is an IP address.
From our perspective, the machineID at the time was necessary, as I explained, to differentiate scans on different computers. It's easy to call from within the JUCE scanner along with OS version etc., for the most part is not considered questionable AFAIK and the alternative would require building out further functionality to allow for custom naming which then complicates things much further.
Just to try explain where we are coming from, other reasons for recording some data like processor specs etc. for example was to try match that against plugin info to determine if a plugin was M1 compatible on and update our database as such... that wasn't fully implemented yet though. We also thought being able to compare hardware with friends when comparing groups would be a useful addition as well as having your specs on hand if you were trying to contact a developer for support.
Anyways, as mentioned, we'll discuss and see if we can find a more explicit means of communicating this at sign in or installation to reduce any potential confusion.
Statistics: Posted by NateKVR — Mon Mar 04, 2024 8:42 pm