Live data from Hacker News

VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

github.com

81–90 of 120 posts

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#81
post #36

H̶m̶m̶,̶ ̶t̶h̶i̶s̶ ̶w̶i̶l̶l̶ ̶n̶o̶t̶ ̶f̶l̶y̶ ̶:̶)̶ ̶ I̶'̶m̶ ̶p̶r̶e̶t̶t̶y̶ ̶s̶u̶r̶e̶ ̶y̶o̶u̶ ̶c̶a̶n̶'̶t̶ ̶j̶u̶s̶t̶ ̶s̶t̶r̶i̶p̶ ̶t̶h̶e̶ ̶l̶i̶c̶e̶n̶s̶e̶ ̶o̶f̶ ̶a̶ ̶s̶o̶f̶t̶w̶a̶r̶e̶ ̶a̶n̶d̶ ̶r̶e̶l̶e̶a̶s̶e̶ ̶i̶t̶ ̶u̶n̶d̶e̶r̶ ̶t̶h̶e̶ ̶t̶e̶r̶m̶s̶ ̶y̶o̶u̶ ̶w̶i̶s̶h̶ ̶i̶t̶ ̶h̶a̶d̶.̶ ̶ ̶h̶t̶t̶p̶s̶:̶/̶/̶c̶o̶d̶e̶.̶v̶i̶s̶u̶a̶l̶s̶t̶u̶d̶i̶o̶.̶c̶o̶m̶/̶l̶i̶c̶e̶n̶s̶e̶ ̶ ̶"̶Y̶o̶u̶ ̶m̶a̶y̶ ̶n̶o̶t̶.̶.̶.̶ ̶s̶h̶a̶r̶e̶,̶ ̶p̶u̶b̶l̶i̶s̶h̶,̶ ̶r…

The problem is they’ve taken a commit that was obviously made in error, and used that to justify the IP contained within that commit being MIT licensed. Sure, this might be legally sound. But it’s certainly scummy. Especially when you consider it’s acting against the wishes of the team that has been working hard over the past years to make a product loved by so many.

If this[0] is indeed the inadvertent commit we’re talking about...how is that code? It’s three URLs in a JSON file, one of which even contains the string “public”!

There’s no proprietary algorithm being described and I’m guessing that those URLs respond with 200 OK without any authentication of where the request is coming from, which says to me the host thinks it’s okay to send me that data. (On mobile or I would check.)

Would it still be a problem if it were forked and the JSON key names were changed or some other alternative method of configuring the URLs were used?

I would understand if the entire source file for interacting with the extension gallery were taken here, but just a config setting?! That says to me that I couldn’t write my own web browser with the default homepage set to Google without permission...

[0] https://github.com/Microsoft/vscode/commit/f1d0c1d88417f85ec...

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#82

Earlier quoted context omitted.

Exactly. I like the idea of having VSCodium as an option but I don’t have an urging need to use this fork since just removing a license and telemetry endpoints doesn’t really add any value compared to the official package.

Removing telemetry adds a lot of value. To each its own, I guess.

It would add value if VSCode didn't allow you to disable it and didn't document what data was sent - but it is documented, and it's trivial to disable it if you choose to do so. I don't see the point of this.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#83
post #78
post #76

Earlier quoted context omitted.

That's a technical response to your technical question. The license is there, in the master branch. I don't see any reverted commit, the code is simply licensed as MIT as far as we can tell.

https://github.com/Microsoft/vscode/commit/f1d0c1d88417f85ec... This is the revert of the mistakenly committed code. In this repository's readme there is a link to a thread where (presumably the author, I didn't check) says that the public should be able to use the proprietary URLs because a commit was made that contained them (the parent of the above), and thus they are open source. While this may be technically tru…

> able to use the proprietary URLs because a commit was made that contained them (the parent of the above), and thus they are open source

You're right about one thing, I don't need to agree with your ethical framework, especially if it means that somehow a URL that I received with no access restrictions or controls, and publicly available data shared behind it, is somehow afforded copyright protections that would restrict me or anyone who received the link from then re-sharing a link to the URL. The courts in US at least have rejected that argument.

> Fortunately, courts generally agree that linking to another website does not infringe the copyrights of that site, nor does it give rise to a likelihood of confusion necessary for a federal trademark infringement claim. [1]

If I took a copy of what was at the URL and redistributed it without receiving a proper license first, then I could be in legal and ethical jeopardy. But simply putting the URL into the product.json file is akin to linking, and the courts seem to have roundly agreed that a Uniform Resource Locator or a Link is a non-infringing form of protected free speech.

At any rate, I hope you see how I may have mis-interpreted what you actually said, as something other than what you've now explained that you meant. It wasn't clear at all.

[1]: http://www.dmlp.org/legal-guide/linking-copyrighted-material...

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#84
post #79
post #71

Earlier quoted context omitted.

Maybe you can show me the actual mistake, because no commit was apparently referenced in either the post I replied to or the parent post.

The parent of this [1] commit was referenced in a thread linked in this repo's readme. I said this in a different thread, but I'll repeat here: I don't believe the community should be trying to find legal "gotchas" such as this one in order to get around reasonable limitations set in place by a team, else teams will begin to stop using as permissive licenses as they do. This is a matter of ethics for me, as the legal…

If you had linked that comment in your first reply, I would have agreed with you and we probably wouldn't have had any of this to talk about :)

A license granted by accident without consideration in return is not a "no takebacks!" situation. If I paid for that license and then you said, it was granted by mistake, I may have a legal leg to stand on in terms of "no takebacks" claims. But if it's just a URL, I'm pretty sure I actually don't need any license or your permission to copy it.

(If you wanted the data that the URL serves up to be protected, then you should have implemented some kind of actual protection scheme, like a token auth system that restricts access to authorized users only, instead of serving that content up to anyone who knows where it is located on the public internet.)

I don't think that's what they've actually tried to do here, so the issue is really moot. Thanks for clearing up what you meant for me, and have an upvote.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#85
post #31

Doesn't have the latest build for macOS. :(

Disclaimer: general comment. Not affiliated with project, etc. I don’t know about you, but I don’t typically feel like shelling out $1000 to buy a machine specifically for an OS I don’t use, just to build a binary to non-paying users of free software. If Apple would provide easily installable ISOs for VBox/VMWare installations (or something equivalent), I might bother setting up a build for it. Right now it’s out of…

IMHO it's easy enough to find a way if you want to test.

I had to do it a few times in the past and it's surprising how easy it is to run macOS in VirtualBox. Insert ISO, change some configuration, and it boots and installs. Plenty of tutorials and such too.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#86
post #48

Earlier quoted context omitted.

Telemetry should not be on by default without express user consent.

It is only without express user consent for those who enter into contracts without reading them. Assuming you aren't one of those people then you consented.

What do you mean? Just to see what you were talking about, I downloaded VSCode from their official website, installed and started it. At no point was I (to their credit) presented with a "contract".

OTOH, there was (again, to their credit), a notification when I started the software about how to disable telemetry.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#87

Earlier quoted context omitted.

Disclaimer: general comment. Not affiliated with project, etc. I don’t know about you, but I don’t typically feel like shelling out $1000 to buy a machine specifically for an OS I don’t use, just to build a binary to non-paying users of free software. If Apple would provide easily installable ISOs for VBox/VMWare installations (or something equivalent), I might bother setting up a build for it. Right now it’s out of…

IMHO it's easy enough to find a way if you want to test. I had to do it a few times in the past and it's surprising how easy it is to run macOS in VirtualBox. Insert ISO, change some configuration, and it boots and installs. Plenty of tutorials and such too.

What ISO? And where?

You mean those hacked ISOs from TPB for 3 year old OSX releases?

How can I, or anyone else for that matter, be sure they are safe to use and represents runtime behavior of the latest ever-changing (read: breaking) OSX?

It’s not as easy as you make it out to be.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#88
post #16

Nice idea. With Chromium there is a bit of a problem with protected video codecs, but I think this doesn't apply to VSCodium.

Well, with Firefox people were complaining about the removal of ALSA support, with the reasoning that people who liked that were also likely to have telemetry turned off. So a downside might be that your usage patterns are not taken into account when using this or turning off telemetry in regular VSCode - though I'd claim that that is to be expected and completely reasonable.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#89

Earlier quoted context omitted.

IMHO it's easy enough to find a way if you want to test. I had to do it a few times in the past and it's surprising how easy it is to run macOS in VirtualBox. Insert ISO, change some configuration, and it boots and installs. Plenty of tutorials and such too.

What ISO? And where? You mean those hacked ISOs from TPB for 3 year old OSX releases? How can I, or anyone else for that matter, be sure they are safe to use and represents runtime behavior of the latest ever-changing (read: breaking) OSX? It’s not as easy as you make it out to be.

How can I, or anyone else for that matter, be sure they are safe to use and represents runtime behavior of the latest ever-changing (read: breaking) OSX?

The Hackintosh community has plenty of very knowledgeable individuals who know what they're doing. If someone was trying to pass malware around they would be found out and ostracised very quickly.

You can also find the direct links to Apple's servers if you search. Hint: InstallESD.dmg and swcdn.apple.com .

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#90
post #46

Earlier quoted context omitted.

Can you share the firewall rules/domains to block to disable telemetry for VSCode?

There's a lot of traffic that comes from VSCode, so it's sometimes hard to tell which is which—e.g. the autoupdate checker, and the "Code Helper" queries to schemastore to get JSON validation configs for the JSON files in your project, and the NPM queries for package.json I block most of it anyway, with a couple of individual exceptions, but other than those examples mentioned above, there's also: - dc.services.visua…

> I actually have no clue what the last one there is (Bing)

workbench.settings.enableNaturalLanguageSearch

Post reply on HN