It gets sent to self-hosted infrastructure so only I can see it.Ĥ. It only concerns basic information about the application and doesn't include identifiers.ģ. It is opt in, and the page asking for the user's consent contains a thorough description of what is collected, how it will be collected, how their personal data is kept away from it, and that nothing bad happens if they say no.Ģ. #How to get anonymous voice in audacity code#I'll admit to having written code on occasion which has the ability to report telemetry, but several caveats apply to every time I've done it:ġ. There are cases where I don't mind the collection of telemetry, but most of the time, it's not valid. Do the same with any telemetry - do the T&Cs restrict the vendor in the way your first sentence suggests? The legal agreement is what matters, not the PR promises. What's the worst case, not the sales patter? If you do that critically you can make an informed opinion about FUD for yourself. Compare the reality of the legal statement with the PR puffery. But read it with a critical eye as to what limits it does or doesn't impose. It's possible they've changed the wording and those limits have been imposed. I think there were a few other bits like that. If they syphon up a few transactions with your bank that's quite OK, their T&Cs allow it. If I conduct a transaction with Microsoft of course they're going to need that." Anyone used to reading more carefully notices what it doesn't say: that they're restricting that to transactions with Microsoft or some affiliate. Innocent reader looks at that and says "Quite reasonable. Have they changed their T&Cs then? Or have you read them? Certainly when I read them the alarm bells were rung no so much as by what they said as to what they didn't say.įor instance they gave themselves permission to extract data about transactions. "t is now extremely easy to restrict telemetry to the functioning of the OS itself, which is entirely reasonable" It is almost certainly true that MS could have explained this period of intense telemetry better and it is largely for this reason that there is still a tremendous amount of FUD about telemetry in general around. Once Win 10 went RTM most of this compulsory telemetry fell by the way-side and it is now extremely easy to restrict telemetry to the functioning of the OS itself, which is entirely reasonable. It is probable that to an extent MS poisoned the telemetry well during the development of Win 10, but this was on pre-release development versions where, understandably, MS were watching almost every interaction with the OS under development. #How to get anonymous voice in audacity professional#It is possibly - probably ? - not the application my ex brother-in-law would use, he is after all a professional sound engineer with his own record label, but for me it does everything I need. I have Audacity installed on both Win 10 and Linux and I am firmly of the opinion that it is a brilliant application. Telemetry is not a subject I have significant problems with so long as it is restricted to how an application behaves and any possible negative interactions with the OS it is installed on. So yes - keep the forks ready, but those forks being ready might well be sufficient to keep the telemetry truly consent driven, and therefore "not an issue". Having a view of the features used by users can be useful beyond just seeing what bug reports they submit. Yes, it's very clearly opt in without negative consequence if I don't, but the point is that telemetry isn't necessarily evil. Various flavours of linux have package popularity (or equivalent) telemetry. I am clearly asked AND I can say no without adverse effects on the operation of the system) The other thing that is universally bad is telemetry that isn't truly consent driven (i.e. What *is* almost universally bad is identifiable data being hoovered up. #How to get anonymous voice in audacity software#If the software checks for updates the first time it is started each calendar week, and that check includes a tag to say which version you are currently running, and on which platform, then that gives some idea to the developers which platforms are being most regularly used with their software - and potentially guides build/design decisions. Telemetry isn't necessarily bad - it very much depends on what is being communicated. This is going to be an unpopular opinion. "Keep the forks ready, kids! This is absolutely going to be tried again, as Mr K does not seem to understand that telemetry is something he wants, not something the users want." Re: Audacity have announced a U-turn on plans to introduce "basic telemetry" into the product.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |