-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please publish this extension on open-vsx registry #10
Comments
Hey :) Could you explain the reasoning? |
Yes. Actually Open VSX store is an open source store for FOSS implementations of VSCode that has Microsoft's telemetry service removed (the one built from VSCode's FOSS code without MS's proprietary stuff) If only it's not an inconvenience for you =) |
Interesting, can you use it as a VSCODE registry? |
No, not really. There are licensing issues. VSCode uses Microsoft's registry, which doesn't allow any FOSS implementation of VSCode to use that marketplace. And Microsoft doesn't allow using any other registry with their build of VSCode. Feel free to close this issue if you feel it's not worth your time to publish to 2 different marketplaces. It's possible to use plugins from Microsoft's registry, but through some extra steps (you can't simply search it in VSCodium's [FOSS VSCode] extensions panel). It's just that some of us like using a non-proprietary software which lacks telemetry. No pressure on you to cater to our beliefs :D |
Wow, never heard of that :) Would you like to use the package there or you are asking for others? |
It would be nice to be able to find the extension directly from there. As of now, I download extensions not avail there from Microsoft store and then manually install them in Codium. Asking it primarily for others because if someone decides to use Codium, they might not know they can manually install extensions from MS store, and they might not be able to find this one for Codium or other FOSS builds of VS Code at all |
Pretty much the title. Thank you <3
The text was updated successfully, but these errors were encountered: