Re:Microsoft Launches Visual Studio Code, a Free Cross-Platf...
by click170 on Wednesday April 29, 2015 @03:35PM
(#9461099)
I agree, there should be an option for that.
But for those who care about their privacy, IMO its approaching the problem from the wrong angle if you're trying to get some developer to change their code to respect your privacy. Its their code. They can do what they want.
We as users should have protections from them attempting to submit information we don't want leaked. To me the solution is better perimeter monitoring and filtering.
While not practical in many situations I would highly recommend filtering all outbound traffic using a new firewall that supports such features (Sophos UTM for one, PfSense for another). Its the only way to know for sure those requests don't get out even when there is a disable option.
But for those who care about their privacy, IMO its approaching the problem from the wrong angle if you're trying to get some developer to change their code to respect your privacy. Its their code. They can do what they want.
We as users should have protections from them attempting to submit information we don't want leaked. To me the solution is better perimeter monitoring and filtering.
While not practical in many situations I would highly recommend filtering all outbound traffic using a new firewall that supports such features (Sophos UTM for one, PfSense for another). Its the only way to know for sure those requests don't get out even when there is a disable option.