335
This is what we call juicing the books
There's a manger who gets paid by copilot commits signed for sure.
It also makes copilot appear more used *and far more reliable.
There’s a manger who gets paid by copilot commits signed for sure.
That manager should be removed
I'm so tired of this shit. Break up Microsoft.
Looks like they are back-tracking, but knowing MS, it won't be fully rolled back, just made slightly less shitty. They locked comments on the PR after the backlash.
Thank you all for your feedback, professional or otherwise. Sorry about the regression. I will work on fixing this in 1.119.
There is a number of issues with the Co-Author functionality:
- It should never have been enabled when disableAIFeatures is on.
- It should not add attribution to changes that were not done by AI.
- We need to make sure it receives a more test coverage before change the default.
am I going insane or does their response sound exactly the same as an LLM justifying a mistake?
Yes, and yes. Pretty sure the same system is used for PR responses by Intel in their repos. The pattern is exact, but then every now and then you get an obvious human.
I'm betting it is
Turned this shit off as soon as I saw it. What a bunch of bullshit. So IDEs have had quote completion features for years and now you want to claim that you "co-authored" my work because you suggested an end-quote and I hit tab? Fuck off, tempted to just disable this shit for my whole org when they change the billing model anyways.
Doesn't this mean it's all completely stealable, because things ai make can't be copyrighted or anything?
He said AI didn't make it, I would assume more than a Co-Authored would be required to ignore licenses, but that's still a gray area anyways, I think?
Gross. This reinforces my existing habit of not trying to integrate everything and instead use specific tools for specific functions. That's kinda unix-like of me, right? lol.
I like using the git CLI client in a standalone terminal window, and might still do so even if Microsoft weren't constantly giving me reasons to never even consider changing.
Is it possible to use VSCodium while, for a lack of a better word, pirating extensions from their store?
Yes, if you want something that's not in OpenVSX, you can go on the VS code store on your browser and download the extension as a VSIX file. Then you can add it to Codium manually.
Oh, I'm very much in favour of this actually. If you use slopgen in any part of whatever you're making, it should be labeled. If it was up to me, that would be a feature that you can only turn off by uninstalling copilot.
Guess someone misconfigured their VSCode?! Seems someone helped them find it.
And seems this is a double-post.
This is the default now: https://github.com/microsoft/vscode/pull/310226
Lol 😆
Feels it should be tied to whether the AI features are enabled.
Product Manager at @microsoft working on VS Code and GitHub Copilot!
Yep, typical PM stuff. The KPI went up!
I think it isn't in VSCodium
VSCodium is the only VSCode I will ever use. Fuck all the Microsoft branded AI bullshit. A few tweaks to a json file is all you need to make Codium work with the Code extension store. Sure, it's against Microslop's ToS but who cares
As a vscodium user i can tell you that is not true. I had to debug a c# unit test this week and for the life of me could not get it to work on vscodium. The c# extension cant run in vscodium and the same is true for the debugger. There are alternatives but it just would not attach the debugger when i hit debug tests.
Installed vscode with the c# extension and it just worked, sadly.
Still using vscodium though haha
Yeah, I realized a while back the only thing holding me to VSCode was Intellisense, when they deprecated that I switched. Codium is my friend now...
https://github.com/microsoft/vscode/pull/313931 Now not anymore
Claude code has given its self credit in the commit message since the beginning. I suspect most people turn that off.
Whoops on the double post, it was meant to go to two separate communities
I hate it but honestly most people are probably using that shit and lying about it in commits.
If this note were added to the commit whenever an LLM were used to author code then this would be a good feature but just silently adding it is so shitty.
I mean I suspect people use AI to write code but disguise it because they know it will upset others so it’s more likely than not that the commit was authored by AI even if VS Code can’t see it.
Anyone dumb enough to leave that setting on probably doesn’t know what they are doing and probably is using AI.
It’s still shit and misleading though and MS shouldn’t do it. I use VS Codium so I need to make sure it doesn’t happen there too.
this post was submitted on 02 May 2026
335 points (99.4% liked)
Fuck AI
6922 readers
1284 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.
AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.
founded 2 years ago
MODERATORS