If you look into the arcane architecture of the Playstation 3 console you quickly gain an appreciation for just how impressive the RPCS3 emulator is. PS3 is definitely one of hardest emulation targets, so it's wild they have the majority of the library working (with enhancements like upscaling and higher frame rates on many of the titles). I guess it's nice people want to help and AI assisted coding can be fine but I…
PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
101–110 of 162 posts
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#102Earlier quoted context omitted.
No, it is a tooling problem. The tooling is telling laymen that they built wonderful things that definitely work and perfectly fix and add features. The tooling gasses them up and is simply wrong in these cases. If your tool regularly lies, gaslights and produces wrong results, that's a tooling issue.
Does the hammer lie to you that everything is a nail? Can a voltmeter _lie_ to you? EE are expected to know when their measurements are wrong. And Professional Engineers are legally accountable for consequences of such mistakes.
Hell fucking yes it can?
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#103Earlier quoted context omitted.
Over the last month, I've been using Claude to assist in some things that were at the edge of my ability (or maybe just a hair's breadth beyond it). I've added features to open source projects that everyone's been waiting years for. I always fork it telling myself that I want to be able to submit PRs, but really I'm just making the changes for myself, since I don't even have the nerve to show it off. If these people…
You could use your changes to show that a feature is useful, but not do a PR. The specific code is no longer that important.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#104I’ve read so many stories like this that I’ve actually gotten scared of making PRs open source projects. There’s one in particular where a feature I really wanted didn’t exist, so I forked and had Codex 5.5 assist with building the feature on my local version. It works perfectly. My life has been improved in being able to have this feature now. Normally I’d want to share it back with the community so others can benef…
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#105Earlier quoted context omitted.
If you're upfront about the provenance and amount of effort that went into it, is there really a problem? I feel like the issue is people contributing code they don't understand and presenting it as if they do.
Quite possibly never tested, of maybe only tested their problem and not if it broke anything else.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#106We've seen a few takes on this kind of issue, but the solution I liked the best was the linux "developers take full responsibility" approach. The "Assisted-by:" tag was a pretty nice touch too. The article unfortunately feels more like a rant than a good exploration of the problem space.
(At least for any coding LLM that isn’t trained entirely on one company’s own code and also offered by that company. That sort of LLM might be able to make the regurgitation argument work for them.)
Thus any project requiring “full responsibility” by submitters may as well just ban submitters from using LLM-based tooling. That’s the tack I’ve taken for my projects, and a number of large projects have taken that stance too.
(Before someone trots out “Technical enforcement of this is impossible!” be assured that such rules are not negated by a lack of technical enforcement; after all, there’s also no way to technically enforce that you didn’t copy someone else’s code and paste it in. But by thinking a lack of technical enforcement matters, you’re outing yourself as someone who will happily violate rules if they think they won’t get caught.)
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#107I recently just started using Claude/ChatGPT/China models for some PS3 homebrew work. Every model seemingly falls flat in this scope of programming. The PS3 is very complex and the tooling is fairly undocumented in a lot of instances. It doesn't surprise me most of these AI PR's are nonsense. If anyone else has attempted writing PS3 homebrew apps using AI and has refined their tooling/systems/automation please let me…
You do realize that’s actually how they work, right? They don’t understand or reason about anything, your prompt and other input is just about trying to guide where the pachinko balls fall in the output.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#108Earlier quoted context omitted.
Similar for me, but regarding the Classic Macintosh APIs. The difference is that there are plenty of books, and some source code available… just not enough to stop Codex from writing subtly wrong gibberish. I get the impression that the “10x velocity!!!!” claims still only reflect which areas have a sufficient corpus to learn from, rather than any inductive reasoning.
You are completely right it's a what is the next token guessing machine so without corpus it's guesses are worse as expected.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#109Perhaps a "wall of shame" showing off bad PRs would make people think twice.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#110-----
OpenCode
4.9k issues 1.7k PRs 158k stars
https://github.com/anomalyco/opencode
-----
Pi
31 issues 4 PRs 47k stars
https://github.com/badlogic/pi-mono
Their secret? A very rigorous contribution policy. Essentially, issues and PRs are autoclosed, and reviewed daily by the team. If its not slop, they whitelist either the issue/PR or the contributor (so their stuff isn't autoclosed next time).
https://github.com/badlogic/pi-mono/blob/main/CONTRIBUTING.m...
GitHub needs an issue / PR approval flow.