Earlier quoted context omitted.
This seems incredibly overblown. According to the diff, all they were collecting is time spent editing certain file extensions, along with a list of installed packages: https://github.com/SideBarEnhancements-org/SideBarEnhancemen... They're trying to figure out what languages people are actually editing on a day-to-day basis, and people here are calling for them to leave the company? Like, really? People have been wh…
So, to use an analogy: "Yeah, we broke into your house and rummaged through your stuff, but it's okay, we were only there to count how many spoons you had. Yes, I know, we could've asked you before we broke into your house, but we tried that before, and for some reasons we had no takers. And it was really important to our researchers that we get a good idea about the number of spoons!"
Kite telemetry code in Sublime package SideBarEnhancements
111–120 of 120 posts
Re: Kite telemetry code in Sublime package SideBarEnhancements
#112At this point I'm really thinking that Atom, Sublime et al are lost causes. If plugins makers will add their own telemetry I'll just go back to vim and be done with it.
Re: Kite telemetry code in Sublime package SideBarEnhancements
#113Re: Kite telemetry code in Sublime package SideBarEnhancements
#114So this is something I'm not sure I've ever said before, but if you work for Kite, you need to quit. Like, I get working for even exploitative companies (though I won't)--economic insecurity is definitely a thing and we all gotta eat. But you can find a job that doesn't involve literally spying on the down-low. I promise you, you can. Abandon these jerks before they bring you down with them. They've demonstrated a wi…
How about, the people running Kite need to shut the company down? People who quit will just be backfilled.
If a couple of employees leave, they'll be limping.
Re: Kite telemetry code in Sublime package SideBarEnhancements
#115So this is something I'm not sure I've ever said before, but if you work for Kite, you need to quit. Like, I get working for even exploitative companies (though I won't)--economic insecurity is definitely a thing and we all gotta eat. But you can find a job that doesn't involve literally spying on the down-low. I promise you, you can. Abandon these jerks before they bring you down with them. They've demonstrated a wi…
Kite is a small fish in the bond... everyone working for FB and Google should be ashamed of themselves for working spy machines. I mean it. It sounds harsh but that's the way it is. But I guess money trumps morals.
If you work for these companies in any capacity you're being highly unethical. End of discussion.
Re: Kite telemetry code in Sublime package SideBarEnhancements
#116Like, did they not think that we wouldn't catch them in the act?
Don't try to steal from thieves.
Re: Kite telemetry code in Sublime package SideBarEnhancements
#117Earlier quoted context omitted.
It's not okay for websites doing this, and any website doing this from May 2018 on will end up fined hundredthousands of dollars every time they do this. The European General Data Protection Regulation [1] is coming, and everyone that doesn't comply with it will have more than just a little problem. No site or program is allowed to track or store anything about me, to transmit anything to a third party, or to even co…
I don't know anything about the regulation and just skimmed the Wikipedia article for a minute, but isn't this regulation unenforceable in practice? If I have a website, how am I supposed to know if a visitor is a citizen of the EU? If my company operates outside of the EU, the EU has no jurisdiction.
How that pertains to a normal website on the internet, I am not sure.
*Edit: At least this is my understanding and my company is already making development plans on how to comply with the new law.
Re: Kite telemetry code in Sublime package SideBarEnhancements
#118Interesting growth model by buying out developers of popular packages and add telemetry or the kite product. You just kill all credibility on the way and you will be outlawed by maintainers etc. We may be many but at certain bottlenecks ethics is still high and with OSS we are able to just fork packages. As companies start to exploit developers trust we have to rethink the security model inside our IDE`s and probably…
Sadly, I think it's what you might call "evil genius".
Re: Kite telemetry code in Sublime package SideBarEnhancements
#119Earlier quoted context omitted.
Seriously. Sublime, Atom, VSCode, and every other platform that supports plugins should all be in crisis mode over the crap Kite's been caught doing. If we can't trust that an addon we installed yesterday is safe today, their platforms just turned into gigantic malware vectors that are totally wide open. This kind of exploitation needs to be stopped immediately.
I work on VSCode. We are aware of the possibility of bad plugins or even good plugins that go bad. The real nightmare scenario would be what's happened with some Chrome plugins, where a widely used plugin is either co-opted or bought out and becomes malicious (even worse if it disguises its maliciousness). All of these package ecosystems are similar to NPM in that they are built on trust and community policing. This…
Without an easy way to know who the package is connecting to, it only instills a false sense of security.
Re: Kite telemetry code in Sublime package SideBarEnhancements
#120Earlier quoted context omitted.
Seriously. Sublime, Atom, VSCode, and every other platform that supports plugins should all be in crisis mode over the crap Kite's been caught doing. If we can't trust that an addon we installed yesterday is safe today, their platforms just turned into gigantic malware vectors that are totally wide open. This kind of exploitation needs to be stopped immediately.
This has definitely always been a concern among certain users of the Package Control community. Since the Sublime Text python environment is run as the user, without a sandbox, it is possible a rogue package would upload all of your data somewhere. So far we've operated under a model of requiring the end user trust the package developer, which isn't going to be the case 100% of the time. We are set up in such a way t…