Skip to content
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

Publish extensions to open-vsx #52

Closed
orblazer opened this issue Jun 16, 2020 · 7 comments
Closed

Publish extensions to open-vsx #52

orblazer opened this issue Jun 16, 2020 · 7 comments

Comments

@orblazer
Copy link

I'm a VS Codium user, a FLOSS version of VS Code, it's the same code but without the Microsoft's telemetry and branding.
I want to request if possible to add the ErrorLens extension on the open-vsx.org market to us doesn't need to works with the Microsoft marketplace as is unclear if it's legal to use it on VS Code forks, see here.

Additional info:

  • This is how to publish a new extension.
@usernamehw
Copy link
Owner

usernamehw commented Jun 16, 2020

Done. No idea if extension itself works or not.

@SuperSandro2000
Copy link

as is unclear if it's legal to use it on VS Code forks, see here.

It is very very unlikely that you as an end user could face any consequences. Worst case they block your requests if you overload their servers. If you are an vscode fork developer you should probably think about this a bit more.

@GitMensch
Copy link

@SuperSandro2000 said

It is very very unlikely that you as an end user could face any consequences."

What a kind of argument is this? There may no consequence if you go to the next shop and take something that you don't pay for, as long as no one sees that... following your note this would be perfectly fine. License breach is license breach.

... and actually Microsoft did say more than once that their market place api should only be accessed by their binary products (including their self-hosted market place server-application, of course).

Many extensions published there (which you can also get via browser) do work fine in vscode forks (other could be made so if adding to product.json) - but why should one try that if there's an alternative available?

@GitMensch
Copy link

@usernamehw The version on open-vsx is quite outdated (currently at 3.1.1) - can you please co-publish recent versions there, too?

@SuperSandro2000
Copy link

but why should one try that if there's an alternative available?

It is more convenient than downloading the files and installing them manually and open-vsx is no alternative because it is missing so many extensions.

I use Microsoft's VSCode alongside and I don't create a loss for them. Also the store comparison is lacking cause it would actually create a loss for the store. If I download the extension twice no matter how I create the same bandwidth usage.

And finally if Microsoft does nothing to prevent private API usage from third party products than maybe they should start doing it.

@GitMensch
Copy link

open-vsx is no alternative because it is missing so many extensions.

https://github.com/open-vsx/publish-extensions gives some insight - and also options - for example I'm no extension developer and wanted to have the language packs without manually needing to download them; then did ask the original author who did not want to do that, added it to the CI by just adding some entries to a json file and problem solved - they are now available and always up-to date.

@GitMensch
Copy link

Thank you for the update https://open-vsx.org/extension/usernamehw/errorlens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants