PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs

Hacker News Top News

Summary

RPCS3 developers are asking users to stop submitting low-quality AI-generated pull requests, highlighting a growing issue of AI 'slop' flooding open-source repositories like Godot Engine.

No content available
Original Article
View Cached Full Text

Cached at: 05/11/26, 12:46 AM

# PlayStation Emulator Devs Beg People To Stop Spamming AI Code Source: [https://kotaku.com/playstation-3-emulator-devs-politely-ask-that-people-stop-flooding-it-with-ai-code-pull-requests-2000694656](https://kotaku.com/playstation-3-emulator-devs-politely-ask-that-people-stop-flooding-it-with-ai-code-pull-requests-2000694656) The team behind RPCS3, the open\-source PlayStation 3 emulator, took to X today to very kindly and civilly request that users “stop submitting AI slop code pull requests” to its GitHub page\. Then they immediately proceeded to tell the AI\-brain\-rotted tech bros attempting to justify their vibe\-coding nonsense to kick rocks in the replies, which is somewhat less civil but far more entertaining to read\. RPCS3 has been around since 2011, and it’s remained the go\-to PS3 emulator of choice for the majority of users since\. If you have ever used it, you don’t need me to tell you that RPCS3 is an extremely impressive piece of software\. In the past few years, the team has managed to make 70% of the PlayStation 3’s library fully playable, bolstered in part by the many users who contribute to its GitHub page\. > Please stop submitting AI slop code pull requests to RPCS3\. We will start banning those who do without disclosing\. There are plenty of resources online to learn how to debug and code instead of generating slop that you don't understand and that doesn't work\. — RPCS3 \(@rpcs3\)[May 9, 2026](https://twitter.com/rpcs3/status/2053248922974605431?ref_src=twsrc%5Etfw) Which neatly brings us to where we are today, because the folks running RPCS3 have clearly had enough of the useless, AI\-coded crap that’s been clogging up its GitHub page\. “Please stop submitting AI slop code pull requests to RPCS3\. We will start banning those who do without disclosing,” stated RPCS3 in a post on[X](https://x.com/rpcs3/status/2053248922974605431?s=20)\. “There are plenty of resources online to learn how to debug and code instead of generating slop that you don’t understand and that doesn’t work\.” Relatively nice way to ask\. Their subsequent replies? Less so, but definitely justified\. My favorite one was when someone asked how the team was certain they weren’t rejecting human\-written code, to which RPCS3[replied](https://x.com/rpcs3/status/2053287528627929517?s=20): “You can’t possibly handwrite the type of shit AI slop we have been seeing\.” Sadly, this isn’t the first time we’ve heard about devs on GitHub getting bombarded with AI\-slop pull requests, and it certainly be the last\. Back in February, Rémi Verschelde, the project manager of Godot Engine, stated that the Godot GitHub page[had become so overrun with AI\-generated PRs](https://kotaku.com/godot-ai-github-code-indie-unity-2000669746)that he was considering hiring more maintainers solely to “deal with the slop\.”

Similar Articles

I don't want your PRs anymore

Lobsters Hottest

An open-source maintainer explains why they now prefer LLM-generated code over community PRs, arguing that AI assistance reduces risk and friction while shifting the value of contributions toward feedback, bug reports, and design discussions.

Pull request limits are cutting down the noise

Hacker News Top

GitHub introduces persistent pull request limits to help open-source maintainers manage contribution volume and reduce low-quality noise, especially from AI-generated pull requests.