News for hackers. Stuff that matters.
Re:Disassembling Sublime Text by ChristianGeek on Sunday December 04, 2016 @03:48PM (#13101698)
Serious question: is there a legitimate reason I should care?
Re:Disassembling Sublime Text by satysin on Sunday December 04, 2016 @04:09PM (#13101786)
Well you should always care about your privacy. I think the better question is do you need to worry? My personal opinion is no, not for things like telemetry in VSCode. It is used to make the product better (hopefully) and I can't see the data collected on startup time or crashes are a massive invasion of privacy.
Re:Disassembling Sublime Text by beefsack on Sunday December 04, 2016 @04:39PM (#13101910)
Is there a legitimate reason a _text editor_ developer should be allowed to make their software call home?

I've only seen Electron-based editors doing metrics, perhaps web developers are less offended by the idea thanks to pervasive usage of things like Google Analytics.

Re:Disassembling Sublime Text by Someone on Sunday December 04, 2016 @05:03PM (#13102019)
There's a lot of information developers could use for the benefit of their users, if they had access to it, some of only very mildly privacy invading, some of it extremely so.

Collecting call stacks from crashing threads or executables can be incredibly useful for fixing them.

Measuring what functionality gets used and what not can help direct feature development (should that checkbox be as visible as it is?)

Collecting statistics on Unicode code point usage may direct development of core data structures (UTF-16 might be the best choice for the basic character unit)

Collecting CPU/memory/disk stats similarly may direct development (if most of your users have gigabytes of free RAM, that change that takes 20% more memory but speeds up things may be useful; if they have plenty of idling CPU! But no memory, things are different)

Knowing what percentage of your users run on a 80386 may help making the decision to compile for at least a 80486.

Knowing internet connection speed and amount of free disk space may help make the decision to move all help online.

Knowing the default browser can help direct testing of the help system, if that system uses the default browser.

Knowing the locale of your users may give hints as to what spell checking languages or UI translations to support.

Having access to the custom dictionaries of all your users may be helpful in improving the ones you ship with the editor.

Having access to every edit made (we are deeply into 'extremely privacy invading' territory now) may also be helpful. For example, you may discover that most of your users don't seem to know about a shortcut that combines five other actions.

Etc, etc.

Re:Disassembling Sublime Text by hartator on Sunday December 04, 2016 @06:05PM (#13102259)
Everything here can be solved by an Apple like pop-up whenever something crashes that ask you if it's okay to send the crash informarion plus machine information.

Telemetry doesn't bring anything more to the table. When I see an app with telemtry, I am just thinking they don't know what they are doing.

Re:Disassembling Sublime Text by Klathmon on Sunday December 04, 2016 @06:45PM (#13102414)
Except for everything that didn't involve a crash (which was everything in that list except the first thing)
Re:Disassembling Sublime Text by 0xcoffee on Sunday December 04, 2016 @05:01PM (#13102013)
An example of how they use telemetry can be seen in their issue tracker.

Here is an example: https://github.com/Microsoft/vscode/issues/707

Re:Disassembling Sublime Text by Skunkleton on Sunday December 04, 2016 @04:49PM (#13101953)
Pretty much all commercially developed software has usage collection. Why is a text editor any different?
Re:Disassembling Sublime Text by khedoros1 on Sunday December 04, 2016 @05:45PM (#13102187)
Exactly. No piece of software should be calling home, except to the degree that its core operation depends on it, and even then, that data should be easily available to the user.
Re:Disassembling Sublime Text by eropple on Sunday December 04, 2016 @05:51PM (#13102205)
So developers should be shooting in the dark on what their users are actually doing with the software and have no data with which to better allocate resources to the features that will cover the most users?

Bold move, Cotton.

Re:Disassembling Sublime Text by izacus on Sunday December 04, 2016 @06:20PM (#13102319)
Developers built great software just fine without constant data spying.... on the other hand all that great "important" data collection somehow doesn't assist in making modern Electron apps any less of a CPU, battery and RAM hogging arse of a software.

Most of analytics data never gets looked at and never provides any useful insight because it's setup poorly.

Re:Disassembling Sublime Text by hashhar on Monday December 05, 2016 @02:51AM (#13103995)
Well, comparing VSCode to Atom I can say that VSCode runs circles around Atom even though both of them are electron based editors.
Re:Disassembling Sublime Text by sooheon on Sunday December 04, 2016 @06:26PM (#13102335)
Yes, developers should have to put some thought into designing their own products. If they're curious how their product is being used, they should do the footwork and ask, and open channels for voluntary feedback. They can collect data with permission. End users' control over their own data is more important than making it easier for developers.
Re:Disassembling Sublime Text by codedokode on Sunday December 04, 2016 @08:03PM (#13102701)
Developers should ask users to opt-in and help with the development. Programs should not send a single byte without users's consent.
Re:Disassembling Sublime Text by khedoros1 on Sunday December 04, 2016 @06:11PM (#13102278)
When they don't provide a method for their user to audit and/or disable telemetry? Yes, I'd prefer them to be blind. I don't expect that this would be a particularly popular position, and that if I kept it as a strict requirement for software I use, it would make it essentially impossible for me to find options in whole classes of software.
Re:Disassembling Sublime Text by zachlatta on Sunday December 04, 2016 @04:58PM (#13102002)
Disappointed by these other answers.

Whether you should care comes down to your ideology. My view: I totally see the value in tracking your users, but I also believe there should always be an option to opt out. Tracking becomes insidious when you lose the right to not participate.

By choosing to opt out, you're showing Microsoft that there are people that genuinely care about being able to not be tracked, making it more likely for them to keep this option for the future.

Re:Disassembling Sublime Text by jsheard on Sunday December 04, 2016 @06:40PM (#13102383)
> By choosing to opt out, you're showing Microsoft that there are people that genuinely care about being able to not be tracked, making it more likely for them to keep this option for the future.

How is Microsoft supposed to know you disabled telemetry? VSCode can't tell them you did, that would be a form of telemetry :P

Re:Disassembling Sublime Text by mook on Sunday December 04, 2016 @10:38PM (#13103231)
They still get update requests (_something_ keeps telling me once a month that there's a new version out, even with telemetry off); that can be compared to the number of unique users with actual telemetry to find the number with it off.
Re:Disassembling Sublime Text by tdrd on Sunday December 04, 2016 @06:41PM (#13102396)
This presumes that MS tracks the fact that you've opted out of tracking, which is not obviously the case.