3 ms·
What's the alternative? Blocking extensions from accessing the Internet? How are you even supposed to do that given extensions already have (completely justifie
by kroltan 4y ago
What's the alternative? Blocking extensions from accessing the Internet? How are you even supposed to do that given extensions already have (completely justified) access to the filesystem and can invoke executables?
There certainly is a valid argument for Internet access, for example for documentation lookup, schema validation, database editing, etc.
There would be a strict, and yet fallible, vetting process on the extension marketplace to make sure every extension complies with whatever rules are defined.
- gabrielgio 4y agoYou have a point. There is no way to block access to resources given the nature of the product, but they could, at least, make more effort to create a better community/environment around the tooling (regarding data handling). > extensions may separately send telemetry, that do not have to adhere to the main VSCode telemetry configuration settings. From what I see things that should never happen and should yield a block from the marketplace. Like you mention, in the end of the day that is not enforceable, but more transparent data privacy policy would show some good faith from their side.
- yjftsjthsd-h 4y ago> What's the alternative? Expose the setting to extensions (if it isn't already), and set a policy in their extension catalog that extension telemetry must honor the global setting. It isn't perfect, but it's better than nothing.