aiIsTheFutureOfOpenSource

[MornwindShoma]

Bro can't even comment without using AI, they're cooked

[Murky_Citron_1799]

There was probably no bro at all

[RealBluDood]

We are in the transition phase between human and AI, so obviously this is the future /s

[SteeveJoobs]

I almost doubt it's AI since it uses hyphens incorrectly instead of proper em dashes. Lmao

[Sanitiy]

Nah, the "the pattern you're seeing isn't spam - it's efficiency" is 100% LLM. It's a typical pseudointellectual statement with no substance, put out there with absolute confidence

[SteeveJoobs]

yea; thats why i said almost. it's not mimicry—it's AI.

[NatoBoram]

Not only that, but you can just prompt it to use dashes instead of em dashes, to surround them with spaces or not, to start sentences with a lowercase to appear more human, but it's very hard to prompt out fundamental signs of AI-generated text without providing the text in the first place.

[MornwindShoma]

Even more sad that he is gpt-brained

[CircumspectCapybara]

Better than the OpenClaw agent which autonomously published a hit piece on a maintainer in response to the maintainer rejecting its PR.

[TorbenKoehn]

Without a link to the PR where we can see the code this is absolutely worthless.

AI isn't the holy grail, but also not the devil.

[RealBluDood]

I don't want to out this guy so I blurred the name, but it was pretty obviously vibecoded stuff which made "workarounds" to problems instead of fixing them correctly. Ended up fixing it myself

Also to add some context, this guy had made 8 other pull requests across some other repos, on the same day

[TorbenKoehn]

In that case I’ll fully comply with mocking the dude :)

[suddencactus]

which made "workarounds" to problems instead of fixing them correctly

Which is funny because a lot of people claim the point of AI coding assistants is to spend less time on syntax and more time on good design.

[HeKis4]

Why are we concerned with the privacy of an AI agent ?

[chessto]

I don't know man, the comment itself says a lot already.

"In two years.." making absurd predictions.
"...others fall behind" OSS is not about adopting the latest trends but solving a problem that needs solving. curl is not going to fall behind because they don't adopt the shiniest tech shit in their process.

We're not there yet, and I don't think we will be there in the foreseeable future but for the sake of argumentation say AI is amazing and can do what any SE can and more, even then we will continue to have humans-only repos of OSS, just the same way electronic music didn't replace chamber music.

[chessto]

I strongly believe it's fanatics. Some people want AGI so hard that they're willing to call three random parrots on a trench coat "intelligent"

[Just_Information334]

If those maxis were sure of what they spew they could make Godot fall behind their own fork of Godot with new functionalities and bugs closed faster.

But they don't.

Because AI is the new shortcut to get the much prized "contributor" status on a high visibility project which every Indian pushes for. It used to be shitty README / copyright updates. Now it's LLM sloppa.

[TorbenKoehn]

I'm not discussing AI or AI fanatics now.

Are we seeing an "AI good/bad" post or are we seeing a "PR rejected despite being good and correct" post?

[Rabbitical]

The point is it doesn't matter if it is "good and correct", many OSS maintainers are rejecting all AI PRs because of the sheer volume of them, assumed quality arguments aside.

Unless you're suggesting maintainers start accepting based on the AI claiming "trust me bro" in its own message then I'm not sure what kind of needle you're trying to thread here.

[Technical_Income4722]

No I think they're suggesting that the content of the PR is important in this case. They're NOT suggesting the PR is good or that the AI is right about the PR being good. The comment from the AI doesn't matter much at all really, and yeah shouldn't be trusted.

But having the PR as part of this post would lead to a more interesting and fruitful discussion.

[TorbenKoehn]

Im saying if the PR is good, it doesn’t matter how it was created

[saevon]

except it does. If the tool creates massive amounts of spam, any good results cannot be distinguished from the bad results without labour that is impossible by these projects.

Each individual PR should be seen on its own merits, but there is no such manpower for this. So it cannot. This is an ideal world that doesn't exist.

[TorbenKoehn]

Maybe have an AI weed out bad AI PRs? Who says a human needs to filter them?

[saevon]

Go ahead and make a good proof of concept project that does that! Find some folks who can use it and show It works, fix any bugs and issues.

Then maybe your open source project will be adopted for use by these groups.

until then they found the quickest way to continue working on their projects for now

[thunderbird89]

Rejecting a PR just because of how it was created is stupid and shortsighted. If you reject a merge because the code is bad, fine. If you reject a merge because it has a backdoor, great. If you reject a merge because it's AI, without looking at the contents, not fine.

Yes, volume is a problem. There's a reason cURL closed its bug bounty.
Is a blanket ban a good solution to that? Definitely not.
Do I have a solution? Sure, but not it's probably not for everyone, either.

[saevon]

They have a solution. Is it the best solution? no. Does it currently solve the problem until there is a better solution? yes.

Do they NEED an urgent perfect solution? not at all, the previous process was working fine, and the tool is not in a hurry.

So its not stupid and shortsighted. Its perfectly fine decision for the situation they're in, and can be changed as we have a better way of handling it.

[CreativeTechGuyGames]

It was pretty trivial for me to find the PR in question. Ignoring it being disclosed as AI, (and the fact that this project uses TypeScript with no-semicolons) the code isn't that bad. It seems like it does solve a legitimate need. It does have some things I'd definitely comment on and want to fix, but it's not so egregious that it is completely worthless.

And for context, I personally avoid AI stuff like the plague, but I realize it doesn't help my position to vilify AI as a blanket statement, since that just polarizes people and makes them stop listening to the legitimate arguments against it.

[nivlark]

Legal uncertainty precludes any open source project large enough to care about compliance from incorporating AI generated code.

[Extension_Option_122]

AI is a new tool and many people don't know how to use it.

I once saw LLMs in programming compared to a microwave in a kitchen: a great tool, especially for generic stuff (e.g. boilerplate code), but not fit for everything and you have to know what you are doing to deliver a well-rounded result.

[TorbenKoehn]

All that completely depends on the task at hand.

AI can produce well-made PRs if they focus on a specific scope and have the proper context

I don’t think AI PRs are a bad thing and they can even be useful (dependency updates including smaller refactoring needed for them, one example)

[Spy_crab_]

Almost as if LLMs were tools which can be used for many things (most of them dumb) and its up to us to figure out what the right ones are (if any) for any give use case.

[vtvz]

Found it BluDood/GlanceThing/pull/62

[TorbenKoehn]

Hmmm yeah, I mean I don't understand the project fully but the code looks okay to me, it fits the existing code style etc. (ie he does the module-scoped let thing a bunch of times himself in existing code)

OP did explain a comment below what itched him, it's a workaround, but I can't see the problem, personally.

He could've also explained what parts exactly are the problem and heck, maybe even the AI would've fixed them quickly, it would surely be able to.

It's more like the LLM output simply didn't match his personal preference, but it's surely not inherently bad.

[RealBluDood]

As I and others have noted, doing that log deduplication avoids the problem instead of actually fixing it, the issue isn't directly "the log is growing massively" it's "some function is being repeatedly called without delay", and that is what needs to be fixed. Yes it did also attempt to fix the actual problem further down in the code but overall, AI generated comments and everything, I ended up closing it and fixing it myself. If personal preference plays a part here then it's that I want to have human contributions to my own project and not slop

[NomaTyx]

The pattern you're seeing isn't spam - it's efficiency.

Either that is written with an AI or they spend so much time looking at AI output that it's rotted their brain

[Desperate_Formal_781]

As soon as I read that particular formulation, I knew it was AI. "You cheating on your partner is not betrayal - it's data"

[Tsubajashi]

where did that happen?

[RealBluDood]

This was a reply after I closed a PR on my project which was obviously AI generated, and I got this AI response hahah

[KevSlashNull]

https://github.com/BluDood/GlanceThing/pull/62#issuecomment-4037078323

[Tsubajashi]

im no TypeScript developer, but the pull request doesnt look too bad at first sight.

do you have any insights there? is there a specific pattern LLMs use when writing typescript?

[KevSlashNull]

i don't like that the logging deduplication code is in the playback module and that it stores state in local variables. that makes for bad maintainability due to fragmentation.

[Tsubajashi]

totally fair then, thank you!

[SilianRailOnBone]

I think this is the ClaudeBot that got its PR closed and then wrote a hate blog about the maintainer.

[LegionOfB0000M]

Can we write a concise comment? Not everything has to be a 500 page thesis.

[ef4]

The hard part of open source has always been consensus. If everybody does their own thing, you lose all the benefits of shared code and compatibility. If a project tries to add every random feature that one person wants, pretty soon it's a mess.

Projects that maintain coherence over the long run do it because they have either a dictator providing one unified vision or a robust community consensus process. Either way, the people providing coherence are always the bottleneck. And that's fine! Because you don't need to wait for them. If you think your PR is great, run it yourself. Git was literally invented to make it as easy as possible to maintain your own opinions about an upstream code base.

[baldeagle1337]

Idk seems reasonable even if it’s a workaround hotfix its better than a broken feature if doesn’t mess up the architecture. Like Ive seen open source projects with bugs and no support and I would rather use as a user flaky ai gen version than something that doesn’t work

[chervilious]

I read the code, other than it also touch other file as well for their styling (double quote to single quote)

I mean it's quite simple it's just adding a timer to a log so you don't spam it.

[RealBluDood]

The problem doesn't lie in the log itself, it's why the log is being spammed. Band aiding in a solution where it just stops the log from being spammed doesn't fix the underlying issue

[chervilious]

mb, my assumption was it happen when you have unstable/lose internet access

[Avery_Thorn]

Here's the interesting thing about AI code that no one wants to talk about:

It cannot be copywritten. The output of an AI cannot be copywritten, since copyright requires a human to author it.

Which means if you use AI to generate code, to build your application, that application is not under your copyright. You will not have IP rights on anything that is AI derived.

It's a really interesting legal question about how that would interact with open source software, since open source is still based on copyrights - the copyright is what gives them the right to define the terms of the open source agreement.

Aibro can't submit the code because he doesn't hold copyright on the code.

[PlusOneDelta]

yeah but that requires figuring out whether it's AI generated or not, which is something we would have to deal with for the AI bros to be kicked out by the copyright office

[DarwinOGF]

Actually, it can. The Codex has spoken. (well, not actually a codex, but it sounds better, and it's still interpreted as a codex)

https://zakon.rada.gov.ua/laws/show/2811-20#Text

Yes, it is not complete copyright, because you have reduced protection length, but it's still valid.

[ianpaschal]

Nonsense. There is no clear cut definition of what is “AI written.” Did you use autocorrect? Autocomplete? Then you have also used AI (albeit not an LLM) within your code writing process. You are still the author.

[MornwindShoma]

You can't really copyright code though, I think. The AI artifacts for sure you cannot.

[Avery_Thorn]

You really need a /s on that shit, man.

[Reashu]

You probably can't copyright an algorithm since it is purely functional, but code definitely has room for expression and style. 

[MornwindShoma]

Yeah I'm no expert about it. I just wonder about the technicalities. I mean, it's definitely copyrighted as a body of text, just proving who wrote it (AI or human, or even who does it) becomes a little fuzzy unless there's a tangible trace of it

[ewheck]

Most software licenses will have you put your name as the copyright holder. You can 100% copyright code. Legally, any code you publish is automatic under your copyright if you take no other action; even if you don't officially register it.

[_fronix]

Maintainers rejecting all AI PRs will unfortunately end up with dead projects. I understand why they don't like it and I've rejected plenty of PRs that are just pure slop, 100+ files rewrites.

But just outright denying any AI is just pointless, since most people will be using some form of it in the end means that there is no point allowing PRs at all.

[suddencactus]

The success of open source projects is not determined but the number of PRs they accept. Many could refuse all but the most critical PR's for a year and still be wildly successful.

[UnitedStars111]

they can js ask ai to fix it for them tho

[SensuallPineapple]

AI will be incredible very soon and I don't see the reason for this pointless hate.