121–130 of 265 posts
Is there any difference between this and the version in Arch's community repo?[0] Obviously VSCodium appears to target more distros. From my experience code (Arch) is entirely debranded, so I can't imagine telemetry was left in. [0] https://www.archlinux.org/packages/community/x86_64/code/
Is there any difference between this and the version in Arch's community repo?[0] Obviously VSCodium appears to target more distros. From my experience code (Arch) is entirely debranded, so I can't imagine telemetry was left in. [0] https://www.archlinux.org/packages/community/x86_64/code/
Is it? I honestly never had a closer look, but the upstream url just points to the regular MS github repo.
Both pull from MS source and are prebuilt, so there should be no telemetry in either. This explains it well:
https://github.com/VSCodium/vscodium#why
In case anyone wants to compare the minutiae:
https://github.com/VSCodium/vscodium/blob/master/build.sh
https://git.archlinux.org/svntogit/community.git/tree/trunk/...
Is this needed? You can disable telemetry from the settings: https://code.visualstudio.com/docs/supporting/FAQ#_how-to-di...
Is this needed? You can disable telemetry from the settings: https://code.visualstudio.com/docs/supporting/FAQ#_how-to-di...
Earlier quoted context omitted.
It's a shame we have to assume the worst. What would be better is for Microsoft to be more transparent about the telemetry and to enable more granular control. That said, I wouldn't bother checking as I don't really care. I rub shoulders with infosec issues daily, as most IT folk do these days. When I think about the perceived risk of telemetry from VSCode, now and in the future it's a negligible risk that I accept.
They are actually very transparent about the telemetry they collect, and they offer granular control. There is a log of all events sent to MS, and a page in settings dedicated to the different types of telemetry they can be enabled.
The "page" in settings consists of just two options, and the complete descriptions of the types of information they collect are "crash reports" and "usage data and errors". That seems the opposite of transparent and granular. Am I missing something?
Earlier quoted context omitted.
VSCode is OSS right? So microsoft’s Work and Investment was specifically designed to be reused without any direct financial compensation. I don’t quite understand your point. Do you think that it’s hypocrtical to use and benefit from OSS work and investment? It seems important to respect the creator’s intent and if software is released under an OSS license it’s not dissonant or hypocritical or bad to reuse, or even m…
This is a clear case of people exploiting and perpetrating FUD (fear, uncertainty and doubt), riding on Microsoft's historic reputation as not being trustworthy, and turning it to their private benefit. If you have trust issues with Microsoft, you shouldn't be using software authored by them, as software can have backdoors and security issues hiding in plain sight (heart bleed bug, for instance). Atom has/had the exa…
Earlier quoted context omitted.
did you read the article you linked? "Logic and critical thinking textbooks typically discuss slippery slope arguments as a form of fallacy but usually acknowledge that "slippery slope arguments can be good ones if the slope is real—that is, if there is good evidence that the consequences of the initial action are highly likely to occur. The strength of the argument depends on two factors. The first is the strength o…
Where's the link between "collecting data on VSCode feature usage" and "gathering a list of all other apps the user has installed on their system and all web searches the user does"?
I can also see them collecting code searches done within the app as a way to check if their search system is working well for real use-cases.
Neither is outside the realm of possibility - you just have to put yourself in the mindset of a dev who is assigned to track down a rare crash or to “improve the search experience” who might want a little more data to work with.
Not saying I agree with any of this collection - it’s terrible and definitely falls under “the road to hell is paved with good intentions”. Companies should be extremely clear about what they will and won’t collect - and never cross the line even if it would be useful.
Earlier quoted context omitted.
I think you’re right, but it needs to be a user choice. If presented with an option, I would likely leave it turned on 90% of the time. I hope this project motivates MS to open source the runtime and making tracking a user- selected option. I really like Code and think MS has really helped the dev community by making it so great and free. But I would like to see them embrace f/l/oss for all their non-core products an…
Isn't it? When I opened VS Code on a new computer for the first time today, a message popped up with step by step instructions to opt out
Earlier quoted context omitted.
They know it. They just don't trust Microsoft.
So they have you install a binary that you can't inspect the source to or build on your own? I'm confused.
So they have created a fork of the project.
Earlier quoted context omitted.
The lack of detailed usage monitoring resulted in more useful software that didn't cater to the lowest common denominator. Telemetry lets you shed all the baggage of supporting the minority.
That’s a bold claim. If the tool is made more useful for majority of the people using it is necessarily not a bad thing.
I guess it manifesta very strongly in the JavaScript community given its propensity for framework fads (LOL)
...