this post was submitted on 02 May 2026
292 points (99.3% liked)

Fuck AI

6885 readers
817 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
 

top 24 comments
sorted by: hot top controversial new old
[–] artwork@lemmy.world 5 points 7 hours ago* (last edited 7 hours ago)

Related:
- [2026-05-03T06:59:30Z] PR#313931 (Change default for git.addAICoAuthor to off...)
- [2026-04-15T21:22:12Z] PR#310226 (Enabling ai co author by default...)

[–] OpenPassageways@lemmy.zip 9 points 9 hours ago

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.

[–] arschflugkoerper@feddit.org 4 points 9 hours ago

Is it possible to use VSCodium while, for a lack of a better word, pirating extensions from their store?

[–] plz1@sh.itjust.works 36 points 18 hours ago

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.
[–] ColeSloth@discuss.tchncs.de 17 points 16 hours ago (1 children)

Doesn't this mean it's all completely stealable, because things ai make can't be copyrighted or anything?

[–] dogs0n@sh.itjust.works 6 points 16 hours ago

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?

[–] panda_abyss@lemmy.ca 143 points 23 hours ago (2 children)

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.

[–] jtrek@startrek.website 32 points 22 hours ago

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.

[–] Zink@programming.dev 17 points 18 hours ago

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.

[–] W3dd1e@lemmy.zip 4 points 18 hours ago (1 children)

I hate it but honestly most people are probably using that shit and lying about it in commits.

[–] ItsMeSpez@lemmy.world 8 points 16 hours ago (1 children)

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.

[–] W3dd1e@lemmy.zip 1 points 15 hours ago

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.

[–] hendrik@palaver.p3x.de 9 points 23 hours ago* (last edited 23 hours ago) (3 children)

Guess someone misconfigured their VSCode?! Seems someone helped them find it.

And seems this is a double-post.

[–] als@lemmy.blahaj.zone 45 points 23 hours ago (4 children)
[–] kungen@feddit.nu 11 points 20 hours ago

Product Manager at @microsoft working on VS Code and GitHub Copilot!

Yep, typical PM stuff. The KPI went up!

[–] hendrik@palaver.p3x.de 13 points 23 hours ago* (last edited 23 hours ago)

Lol 😆

Feels it should be tied to whether the AI features are enabled.

[–] ChaoticNeutralCzech@feddit.org 9 points 22 hours ago (1 children)

I think it isn't in VSCodium

[–] YoSoySnekBoi@kbin.earth 19 points 21 hours ago (2 children)

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

[–] DacoTaco@lemmy.world 5 points 13 hours ago

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

[–] MalReynolds@piefed.social 4 points 16 hours ago

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...

[–] Jason2357@lemmy.ca 5 points 17 hours ago

Claude code has given its self credit in the commit message since the beginning. I suspect most people turn that off.

[–] als@lemmy.blahaj.zone 6 points 23 hours ago

Whoops on the double post, it was meant to go to two separate communities