Closed DeveloperKev closed 1 year ago
The best would be to fork the extension and remove the telemetry from it.
But the license is weird. It's a MIT but at the begin you can read:
Additional binary files may be downloaded at runtime after the initial installation; these are governed by the more restrictive proprietary license terms found at [RuntimeLicenses](https://github.com/microsoft/vscode-cpptools/blob/main/RuntimeLicenses).
RuntimeLicenses state:
All VS Marketplace extensions, including this C/C++ Extension for Visual Studio
Code, must also be used consistent with the VS Marketplace Terms of Use at
http://aka.ms/VSMarketplace-TOU
which exclude to run those files on VSCodium...
The best would be to fork the extension and remove the telemetry from it.
But the license is weird. It's a MIT but at the begin you can read:
Additional binary files may be downloaded at runtime after the initial installation; these are governed by the more restrictive proprietary license terms found at [RuntimeLicenses](https://github.com/microsoft/vscode-cpptools/blob/main/RuntimeLicenses).
RuntimeLicenses state:
All VS Marketplace extensions, including this C/C++ Extension for Visual Studio Code, must also be used consistent with the VS Marketplace Terms of Use at http://aka.ms/VSMarketplace-TOU
which exclude to run those files on VSCodium...
thanks for the quick reply. can i get a hint about removing telemetry & disabling binary bloatwares from installing at runtime, which json file exactly?
Also, can u confirm if the telemetry of the extension still work under vscodium?
In general, VSCodium do not remove/disable any telemetry found in an extension from the marketplace.
So yes, the telemetry still works for vscode-cpptools
and use the lib @vscode/extension-telemetry
.
A quick search for sendTelemetry
in the source will indicate you the files to modify.
In general, VSCodium do not remove/disable any telemetry found in an extension from the marketplace. So yes, the telemetry still works for
vscode-cpptools
and use the lib@vscode/extension-telemetry
. A quick search forsendTelemetry
in the source will indicate you the files to modify.
i did find a bunch of telemetry functions on extension source. I was curious if its possible to remove the telemetry lib from core (by modifying build jsons, then creating custom builds) as if it wasnt there. pls let me know.
In general, VSCodium do not remove/disable any telemetry found in an extension from the marketplace. So yes, the telemetry still works for
vscode-cpptools
and use the lib@vscode/extension-telemetry
. A quick search forsendTelemetry
in the source will indicate you the files to modify.i did find a bunch of telemetry functions on extension source. I was curious if its possible to remove the telemetry lib from core (by modifying build jsons, then creating custom builds) as if it wasnt there. pls let me know.
Maybe that repository will help you understand how to to de-blob and remove telemetry because I think the situation is very similiar (the debugger is closed source). In here the debugger was replaced by samsung's MIT licensed one.
Is there an alternative for this extension?
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.
Hi team, it's been a year or so, i'm using vscodium. its good. As a c++ coder, i'm in love with this extension: https://github.com/microsoft/vscode-cpptools is there any possibility to completely remove telemetry from that? so, the extension repos could be made much broader.