Earlier quoted context omitted.
I can’t access that LinkedIn link without going through their Persona ID process, which requires all kinds of PII. > LinkedIn users attempting identity verification may be unknowingly handing sensitive personal data to Persona Identities Inc., a company that distributes information to government agencies, credit bureaus, utilities, and mobile providers. ^ Link from a LinkedIn page I found on a Kagi search. I can view…
I'm here, what would you like to know?
VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
411–420 of 917 posts
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#412Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#413Earlier quoted context omitted.
Chrome is a now-somewhat-archaic term for GUI (or specifically the actual elements of the GUI, not the concept), and Netscape/Mozilla did use the term a lot. Google claims that their browser is called Chrome because of an association with fast cars (presumably Google was keen to market it to extremely old people, chrome not having been a particularly big thing in cars for a very long time).
> Google claims that their browser is called Chrome because of an association with fast cars FWIW, before Google Chrome, Firefox was originally Firebird (changed for name collision reasons), and Mozilla had broken off the rest of the Netscape-ish "communications suite" into Thunderbird, both arguably named after cars. Besides the use of chrome by Netscape/Mozilla that you mention, roughly around that time I heard it…
The browser was considered slow and bloated however, and when Firefox came, its lack of theme support was perceived as part of it having been de-bloated.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#414Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#415Earlier quoted context omitted.
I think there’s a few of us who appreciate you being up front. I’d question the intent and why it was a mistake, especially when the commit[0] message reverting said functionality states “widespread criticism” citing this very HN article makes it look seemingly like the revert is due to negative PR opposed to a mistake. [0] https://github.com/microsoft/vscode/pull/313725/commits/1e70...
Author of that PR doesn't seem to be a Microsoft employee. Keep in mind that anyone on GitHub can create PRs against VSCode.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#416I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation. There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here - many similar tools do this as well. Obviously, it should not be on…
- a project manager vibe-coded the change without thinking it through at all
- the PR was reviewed by an LLM
- an actual engineer gave LGTM without really reviewing the changes, trusting the LLM
Did I get this right?
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#417Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#418Earlier quoted context omitted.
It wasn’t AI that brought us Apple’s gray on slightly-lighter-gray UI standards, nor the 10,000,000 ••• menus that have infested every webapp in the past 10 years as an alternative to thoughtful UI design. We humans made everything shitty before we made AI.
> Apple’s gray on slightly-lighter-gray UI standards It's a tangential point, but I turned on System Settings -> Accessibility -> Display -> Increase Contrast (the on/off option, not Display Contrast) and now at least the windows are outlined sharply.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#419Earlier quoted context omitted.
> And then set fire to the whole thing in an offering to their robot gods. It's the bourgeoisie dream: A means of production that also does the labor 24/7 and can't complain, infinitely spawnable. Theoretical slavery+, so of course they're throwing everything into the furnace for it.
These next few years are the real turning point. If they are right about AI and robotic workforces, then it's checkmate--they don't need us anymore, and we're next for the furnace. If they're wrong... well, I don't know... Will there be any consequences? Maybe a few people lose a few percent of their net worth.
Robotics isn't even 1% of the way to replacing anything.
Consider why every neat demo is a backflip and not washing the dishes or laying bricks or something.
Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
#420I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation. There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here - many similar tools do this as well. Obviously, it should not be on…