Live data from Hacker News

We will ban you and ridicule you in public if you waste our time on crap reports

curl.se

161–170 of 653 posts

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#161
post #11

I've been helping a bit with OWASP documentation lately and there's been a surge of Indian students eagerly opening nonsensical issues and PRs and all of the communication and code is clearly 100% LLMs. They'll even talk back and forth with each other. It's a huge headache for the maintainers. I suggested following what Ghostty does where everything starts as discussions - only maintainers create issues, and PRs can…

I contribute regularly to some major open source projects and it’s happening here too. So many issues that aren’t issues. Constant “fixing” of documentation that doesn’t need to be fixed. Bug reports that aren’t bugs, followed by a bad PR “fixing” the “bug.” Or YOLOing an LLM PR to change major behavior that users are relying on. And I click and the authors are always brand new, with only vibe coded or examples projects in their history, and have some truly awful LLM generated GitHub “about me” page complete with emojis and links to their GitHub “projects.”

My suspicion is somehow the perception became that if you’re brand new and land a PR in a major open source repo (even as simple as rewording a phrase in a doc that doesn’t need to be reworded), that would help them get a job (they’re always Open to Work on their GitHub about me page).

It’s so much noise that it’s hard to find the real issues.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#162
post #79

From https://curl.se/docs/code-of-conduct.html : "As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities" Why have a code of conduct while being hostile to contributors? I think they should handle this differently.

Perhaps because they are not really contributors, so it doesn't apply.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#163

Earlier quoted context omitted.

You know who also needs a lot of micro-management but doesn’t live in a time zone, is way faster than offshore contractors, scales up and down instantly, has no onboarding period and is (still) cheaper? Opus.

Ehh nothx. I like my slop human powered

Random interjection: if all roads lead to management, I guess I'd prefer a robot

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#164
post #104
post #61

Earlier quoted context omitted.

This sounds like a real cross-cultural mismatch, but it’s doing too much work with nationality alone. In a lot of Indian (and broader South Asian) work contexts, questioning instructions can be read as challenging authority or admitting incompetence, so people default to executing without asking. That’s often reinforced by education systems and contractor dynamics where producing something quickly feels safer than pa…

Yeah, I agree, the time zones are killer , and this can't be ignored. I work at a company spread over most of the world, with SMEs coming and going as the globe spins. Back-and-forth iteration and consultation is a genuinely hard problem. Certain kinds of feedback cycles have a minimum latency of "overnight". Which means we need to invest heavily in good communication. But also, it means more people need to have the…

> But also, it means more people need to have the "big picture", and they need to be able to make good decisions (not just arbitrary ones). So the ideal goal is to prevent people from going off in random nonsensical directions based on miscommunication, and equip them to actually think strategically about the overall plan. Continent X might make different decisions than continent Y, but they're all talking, and enough people see the goal.

Very common pattern you see in literature about military strategy, actually. The answer is delegation, heavy use of NCOs, and in general explaining the plan all the way down to the individual soldier. Under the western school it all falls under "initiative".

Notably, a lot of non-western militaries are terrible at it, and a number of military failings in africa, the middle east, and the soviet union (*cough*russia*cough*) are viewed as failures in flexibility with very low initiative, as well as lacking/unskilled NCO corps.

Dunno how you apply that to an organization, but maybe sending skilled workers as a kind of non-comissioned officer could work. Who knows.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#165

Why is cURL specifically receiving so many slop contributions? Or is this a recent phenomenon for every open-source project, and cURL are the ones most spoken of? First time commenting on HN!

They offered a bug bounty, so people think "let me just use ChatGPT to make money for myself".

But from I hear it affects other projects too. It affected curl more because with the bug bounty they actually need to invest work and look at those.

[1] https://daniel.haxx.se/blog/2024/01/02/the-i-in-llm-stands-f...

[2] https://daniel.haxx.se/blog/2025/07/14/death-by-a-thousand-s...

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#166

Long time ago Sourceforge and then GitHub promoted into the current default the model of open source distribution which is not sustainable and I doubt it is something that the founding fathers of Free Software/Open Source had in mind. Open source licenses are about freedom of using and modifying software. The movement grew out of frustration that commercial software cannot be freely improved and fixed by the user to…

    has nothing to do with open source

    long time ago
Sourceforge is almost 30 years old. GitHub almost 20.

How long does something have to be done a certain way for it to be "to do with"?

I would say we're now two generations deep of software engineers who came up with open source software commonly being mediated through public issue trackers.

That isn't to say it needs to stay that way, just that I think a lot of people do in fact associate public project tracking with open source software.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#167
post #11

I've been helping a bit with OWASP documentation lately and there's been a surge of Indian students eagerly opening nonsensical issues and PRs and all of the communication and code is clearly 100% LLMs. They'll even talk back and forth with each other. It's a huge headache for the maintainers. I suggested following what Ghostty does where everything starts as discussions - only maintainers create issues, and PRs can…

Reminds me of this Indian GitHub tutorial on how to open a PR on GitHub. The video got millions of views and has flooded a specific repo with countless README update PRs of people (mostly Indian) trying to append their name to the README.

Article about it here: https://socket.dev/blog/express-js-spam-prs-commoditization-...

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#169
post #11

I've been helping a bit with OWASP documentation lately and there's been a surge of Indian students eagerly opening nonsensical issues and PRs and all of the communication and code is clearly 100% LLMs. They'll even talk back and forth with each other. It's a huge headache for the maintainers. I suggested following what Ghostty does where everything starts as discussions - only maintainers create issues, and PRs can…

> Indian students Is this cultural? I ran a small business some years ago (later failed) and was paying for contract work to various people. At the I perceived the pattern that Indian contractors would never ever ask for clarifications, would never say they didn't know something, would never say they didn't understand something, etc. Instead they just ran with whatever they happened to have in their mind, until I cal…

How much are the contractors being paid?

The people having a terrible time with Indian contractors always deal with folks making 3k-10k USD/year. Of course the quality is bad.

For reference:

Good Indian devs out of college make atleast 30k USD. Good senior devs make atleast 50k. The really good ones make much more. Most American companies outsource to bottom of the barrel contracting companies like Infosys.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#170
This note isn't going to stop even 1% of the jackasses who would have submitted AI slop.

There are much better ways to communicate the intended message. This comes off as childish to me and makes me think that I'd rather not contribute to the project.

Post reply on HN