Live data from Hacker News

VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

github.com

381–390 of 917 posts

Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

#382

I 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…

Why does the commit editor hide the coauthored message? Why not pre-populate the text field and users take or leave it when committing?

Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

#383
post #57

The best part is that copilot commented on the PR saying that this doesn’t actually change the behaviour, creates inconsistency in the codebase and suggested reverting the change! (This comment seems to have been ignored…) > The configuration schema default was changed to "all", but the runtime fallback in extensions/git/src/repository.ts still calls config.get('addAICoAuthor', 'off'). This is now out of sync and can…

That's pretty standard review practice in there by now.

But it was apparently ignored.

Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

#384

Earlier quoted context omitted.

Who is investing in NFTs today? Who is building their company using permission-less blockchain as the database? The average person still uses a bank checking account, not replacing it with a crypto account. I haven’t heard of any progress on tokens in the Governance direction. Stablecoins without a public audit trail have so far stayed relevant, but there are several which are suspiciously reminiscent of the mistakes…

NFTs are stupid. But I have a feeling as governments default on their debt and economies collapse in the next few decades cryptocurrencies will be of increasing importance.

Cryptocurrencies are now useless, considering how openai and similar companies have enough compute to highjack them and the AI thing might not work out at all…

Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

#385

Earlier quoted context omitted.

I really don't think open models will lose. I think they are cheaper to train because they have to be more efficient than the monstrosities we have now. There is no theory that says the current frontier models cannot exist in models with 1/100th the compute waste ;). When we start trending in that direction, and oh wow we truly are, there will be no reason for these services. You could run them on your own hardware w…

I’m interested in learning more about your theory that these models can be trained more cheaply. Is anyone doing it from scratch, rather than adversarial distillation?

It is a lot cheaper to train a 27b model such as qwen3.6 which you can even vibe code or agentic code with than it is to train a 1t+ parameter model. It runs on a single commodity GPU for goodness sake

It's not a theory. These smaller models that are coming out are huge advances for the field.

I can't comment on companies training practices. That would be proprietary stuff I guess. I think the claims that the advances being made are due to distillation alone are completely unfair. The advances alone are not just data.

Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

#386
post #312

Earlier quoted context omitted.

I'm here, what would you like to know?

Why did you lock the comments on the GitHub issue? (Edit: I meant to say PR, not issue...)

I'm not him, but it was pretty obvious that the comments section was going to be attracting more and more people saying the same thing that had already been said before, and that no useful discussion was going to be had. At some point the value of spamming everyone who commented on the issue with a notification (which puts an email in your inbox if you haven't changed the default setting) becomes lower and lower.

I've seen that before on other issue comment threads. The repo owner says "Hey everyone, if you want an issue fixed, please upvote the issue with a thumbs up". And many people don't read that, and instead post "Please fix this" comments without giving a thumbs-up to the issue. So, 1) the repo owner doesn't get to use the "sort issues by # of thumbs-up reactions" to see the priority of that issue, and 2) everyone who has subscribed to the issue gets spammed with a message that's useless to them.

Since nearly all the new comments had become "me too"-style comments, which should have just been a thumbs-up on a previous comment in order to reduce spam, I feel like locking the issue thread was the right move at that point, to stop people from receiving yet more unnecessary email in their already-overflowing inboxes.

Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

#387

One fascinating thing about the whole AI phenomenon is how incredibly hostile it is to _standards_. Whether something works properly, or is ethical, or is true, no longer matters at all; all that matters is "pls use our AI". Microsoft spent literal decades rehabilitating their reputation. And then set fire to the whole thing in an offering to their robot gods. And it's not just them. There was a time that Google care…

> There was a time that Google cared deeply about UX Have we been using the same Google?

This comment and a few others here make me feel old and sad for the people too young to remember that time. Yes, Google was an enormous breath of fresh air when it came out. 1000% better UI and features than the competition. Search was incredible. Gmail was a revelation. The whole company culture was night and day compared to the stodgy old tech companies like IBM. Just mind blowingly awesome. And then maps?? How did they even do that? The tech world felt entirely fresh and new and hopeful.

Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

#388

Earlier quoted context omitted.

> greed Is a greed/not greed scale really useful to discuss company behaviors ? I wanted to say I get what you mean, but even thinking about the company I root for the most, I can't think of a point where they're not driven by their desire to make a lot more money. If your point is that there's good and bad ways to seek money, I'm not sure it's properly encompassed by "greed", which I interpret as the intensity of a…

Approximately everybody would like more money. Greedy people put the desire for more money above the welfare of the business, themselves, and other. Greedy people literally put their desire for more personal wealth above the very lives of others. Greed/not greed is a very fair way of putting it. One can operate a business that requires profit without wanting to destroy everyone and everything that stands in the way o…

> Greedy people put the desire for more money above the welfare of the business

In my experience, it's much simpler.

People are greedy if they make things I want cost more.

Re: VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

#389

I 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…

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.
Post reply on HN