Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

curl.se

Post reply on HN
Print view View original

21–30 of 653 posts

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

#21

Post by hobs »

dotancohen wrote: post #18
jraph wrote: post #3

Context: [1, 2] > Open source code library cURL is removing the possibility to earn money by reporting bugs, hoping that this will reduce the volume of AI slop reports. > cURL has been flooded with AI-generated error reports. Now one of the incentives to create them will go away. [1] https://news.ycombinator.com/item?id=46701733 [2] https://etn.se/index.php/nyheter/72808-curl-removes-bug-boun...

Money for a report and a patch, with convincing test cases, might be worthwhile. Even if a machine generates them.

To be clear, no, it is not, because of the opportunity cost of all the other slop. That's what this is all about.

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

#22

Post by mikkupikku »

skeptic_ai wrote: post #19
nchmy wrote: 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…

Why you don’t just put an AI guardian to close or to ask them to change the story. Or shadow ban

Subjecting every real contributor to the "AI guardian" would be unfair, and shadow banning is ineffective when you're dealing with a large number of drive-by nuisances rather than a small number of dedicated trolls. Public humiliation is actually a great solution here.

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

#23

Post by mrspuratic »

diffuse_l wrote: post #9

The policy link[0] page still has a link to the bug bounty program[1] which still discuss monetary compensation. [0] https://curl.se/dev/vuln-disclosure.html [1] https://curl.se/docs/bugbounty.html

Although it's not mentioned in those, it's going away at the end of the month: https://news.ycombinator.com/item?id=46701733 https://news.ycombinator.com/item?id=46678710

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

#24

Post by moralestapia »

nchmy wrote: 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

How do you know this?

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

#25

Post by creata »

dotancohen wrote: post #18
jraph wrote: post #3

Context: [1, 2] > Open source code library cURL is removing the possibility to earn money by reporting bugs, hoping that this will reduce the volume of AI slop reports. > cURL has been flooded with AI-generated error reports. Now one of the incentives to create them will go away. [1] https://news.ycombinator.com/item?id=46701733 [2] https://etn.se/index.php/nyheter/72808-curl-removes-bug-boun...

Money for a report and a patch, with convincing test cases, might be worthwhile. Even if a machine generates them.

> Even if a machine generates them.

That sounds wonderfully meritocratic, but in the real world, a machine generating it is a very strong signal that it's bullshit, and the people are flooding maintainers using the machines. Maintainers don't have infinite time.

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

#26

Post by johnisgood »

hobs wrote: post #21
dotancohen wrote: post #18

Earlier quoted context omitted.

Money for a report and a patch, with convincing test cases, might be worthwhile. Even if a machine generates them.

To be clear, no, it is not, because of the opportunity cost of all the other slop. That's what this is all about.

Then no bug reports and no fixes. Sounds good enough.

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

#27

Post by yawboakye »

mikkupikku wrote: post #15
nchmy wrote: 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…

Heh, reminds me of that free T-shirt contest thing... Submit crap PRs to random FOSS projects for a chance of winning a shirt, what could go wrong? https://ongchinhwee.me/shitoberfest-ruin-hacktoberfest/

worked well for a bit. but then the program became popular and that’s when it hit the curb. terrible loss, imo. it was a brilliant idea to encourage open source work with a token reward. it relied heavily on good intentions, which quickly disappeared with the popularity.

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

#28

Post by normie3000 »

nchmy wrote: 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've seen this - it's tiring even at low volume. Goes something like:

Someone creates a garbage issue. Someone else asks to be assigned. Someone from the project may say "we don't assign issues" (this step has zero effect over later steps). Someone else submits a PR. Maybe someone else will submit another PR. Maintainers then agonise how they can close issues and PR(s) without being rude or discouraging to genuine efforts.

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

#29

Post by compounding_it »

nchmy wrote: 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

Resume glorification and LinkedIn / GitHub profile attention do that.

I am seeing a lot of people coming up with perceived knowledge that's just LLM echo chambers. Code they contribute comes straight out of LLMs. This is generally fine as long as they know what it does. But when you ask them to make some changes, some are as lost as ever.

Torvalds was right, code maintenance is going to be a headache thanks to LLMs.

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

#30

Post by rednafi »

Creating crap vuln reports or PRs on popular OSS projects has been an issue long before LLMs. Remember Hacktoberfest?

Students would often abuse it since there’s no adult in the room to teach them how to behave. I guess this is one hard way to f around and find out. But this is by no means condoning this sort of behavior.

Point is, LLMs made the situation more dire: it’s cheap to generate code, whereas reviewing still scales sublinearly. The only way to prevent this is by being rude to people who are rude to you.

Post reply on HN