News for hackers. Stuff that matters.
Re:OBS Studio 33 by rgovostes on Saturday October 24, 2026 @04:27AM (#50219264)
There are a handful of comments here rueing buggy behaviors. These days with nearly the same amount of effort to post a complaint you can delegate the task of reproducing the issue, diagnosing the root cause, and proposing a fix. Yes, it may incur a small to moderate cost, but it's a contribution to an open source project that apparently provides some value in return.
Re:OBS Studio 33 by no-name-here on Saturday October 24, 2026 @07:41AM (#50220342)
> There are a handful of comments here rueing buggy behaviors. These days with nearly the same amount of effort to post a complaint you can delegate the task of reproducing the issue, diagnosing the root cause, and proposing a fix. Yes, it may incur a small to moderate cost, but it's a contribution to an open source project

That would violate OBS's rules - they disallow AI-written code (or write ups) being submitted. Additionally, if you put nearly the same amount of effort into it as writing up the original bug - i.e. pretty low effort - they say that may result in a project ban.

Re:OBS Studio 33 by damowangcy on Saturday October 24, 2026 @06:21AM (#50219847)
I think this is what the whole "AI killed software" fallacy came from.

>nearly the same amount of effort to post a complaint you can delegate the task of reproducing the issue, diagnosing the root cause, and proposing a fix.

Is the effort the same though?

And even it is the same, making a meaningful contribution to an open source project doesn't mean just fixing your problem, but you also need to stay in line with the contribution guidelines, the project's direction and many more, which takes much more effort than just vibe coding a version for yourself.

Building software for one and for a bunch are two different things. AI is good at the former and can be used for the later but not without much effort. Models will get better, true, but that doesn't mean we need less engineering, in fact we need more to stay up-to-pace with AI. Imagine everyone submitting a PR to fix a bug, how fast can you review it manually? And if you use AI to review/verify them, the cost just shift from person who submitted the PR to the open source maintainer.

That doesn't mean AI is bad but that we need new systems and rules.

Re:OBS Studio 33 by mystifyingpoi on Saturday October 24, 2026 @04:52AM (#50219375)
Okay, I'll bite the bait. Assuming that I am a regular user (think gamer), I have a Windows PC, no dev tools, no AI subs or accounts, no GitHub. How specifically can I do the steps required to propose the fix they way you suggest?
Re:OBS Studio 33 by wpm on Saturday October 24, 2026 @05:15AM (#50219487)
How did you end up on Hacker News?
Re:OBS Studio 33 by ro_bit on Saturday October 24, 2026 @05:25AM (#50219532)
address bar
Re:OBS Studio 33 by Rapzid on Saturday October 24, 2026 @07:28AM (#50220251)
Sir, this is a Wendy's..
Re:OBS Studio 33 by cobbzilla on Saturday October 24, 2026 @09:03AM (#50220871)
paste a link to this HN article and then your comment into your favorite LLM, it will be happy to guide you.
Re:OBS Studio 33 by lynndotpy on Saturday October 24, 2026 @09:10AM (#50220926)
I'm not the person you are replying to, and I am with you. I disagree with the suggestion it's trivial to reproduce, diagnose, and fix a bug.

But at https://obsproject.com/help we see OBS has a Discord (regular gamer), a Forum, a Feedback page, and a Mastodon.

Re:OBS Studio 33 by d5lt5 on Saturday October 24, 2026 @04:44AM (#50219339)
That's two fallacies at the same time!

* Appeal to personal responsibility;

* False equivalence.

I'll strike those off my bullshit bingo card.

Re:OBS Studio 33 by rgovostes on Saturday October 24, 2026 @05:23AM (#50219524)
"Appeal to personal responsibility" is not a fallacy. Get a different bingo card.
Re:OBS Studio 33 by rightnutwingjob on Saturday October 24, 2026 @06:19AM (#50219827)
Fair chance not everyone here has the same skill set, motivations, predispositions, and so on and so forth.
Re:OBS Studio 33 by simonra on Saturday October 24, 2026 @04:46PM (#50225062)
If all you do is complain you'll find yourself left out, for good reason. The internet is really not all that different when it comes to this, if you consume other people's emotional energy without ever giving anything back it would be unhealthy to interact with you, regardless of where or why.

The bigger issue is perhaps whether one views someone else politely pointing out something they would like to see improved/changed as a complaint. I suspect a not insignificant portion of users of English unfortunately would interpret it that way. However, the ubiquity of the LLMs might give us some hope that the sending side over time ceases contributing to the problem by saddling the people they wish to freely sacrifice their lifetime for them with their frustration.

Re:OBS Studio 33 by d5lt5 on Saturday October 24, 2026 @09:14AM (#50220954)
> "Appeal to personal responsibility" is not a fallacy.

It is one when you deflect criticism instead of addressing it. Maybe you should have read more than the first sentence after you googled what a fallacy is.

Re:OBS Studio 33 by bulbar on Saturday October 24, 2026 @04:58AM (#50219398)
I tend to agree with you, but why calling it "bullshit"? You can disagree and have a discussing without belittlering other people.
Re:OBS Studio 33 by thebruce87m on Saturday October 24, 2026 @06:00AM (#50219707)
Out of interest- what is your recommended path for this? I mean the path of least resistance where I don’t even have to check out the code locally or similar.
Re:OBS Studio 33 by wizardcm on Saturday October 24, 2026 @06:20AM (#50219841)
Officially and unofficially, the most you need to do is create an Issue report with valid reproduction steps. You'd be surprised how quickly some issues get fixed just because someone finally provided the missing link in an Issue.
Re:OBS Studio 33 by dylan604 on Saturday October 24, 2026 @10:46AM (#50221775)
Yeah, I don't agree that using an LLM to generate a PR in a code base is the best line of action. I could see using an LLM to generate information to provide to create an Issue with would be potentially useful. It doesn't generate code in a way that may not be in the project's style. It doesn't hide anything from the devs. Instead, it points the devs to the specific problem and allows the devs to grok what/why/how of the issue. As we've all seen before (I'm assuming), fixing a bug in one place might not be the best fix place for the fix or a fix might reveal an issue somewhere else.
Re:OBS Studio 33 by cwillu on Saturday October 24, 2026 @04:46AM (#50219350)
That's not even remotely true.
Re:OBS Studio 33 by TomGarden on Saturday October 24, 2026 @04:43AM (#50219337)
Love this
Re:OBS Studio 33 by sick_of_slop on Saturday October 24, 2026 @06:37AM (#50219933)
https://github.com/obsproject/obs-studio/blob/master/CONTRIB...

> All text and content submitted to our project, which includes code, descriptions, issues, and comments, must be human written.

> The use of GitHub Copilot and other assistive AI technologies is heavily discouraged.

> Low-effort or incorrect submissions that are determined to have been generated by, or created with aid of such systems may lead to a ban from contributing to the repository or project as a whole.