this post was submitted on 28 Feb 2026
59 points (96.8% liked)
Technology
82070 readers
5325 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Luckily, the word "Certainly" is a huge hint that it was generated by AI. You know that the reporter of the "issue" copy-pasted the question of the developer right into the LLM and copy-pasted the output right into hackone.
Hindsight bias. This is from 2023. It's obvious now. If it still was this easy to spot they wouldn't have closed the bug bounty program.
It was volume that was more the issue with the bug bounty program.
They were flooded, and recognising it is all well and good, but not if there's no good way to filter it out, not without massive collateral.
I encourage you to read some threads linked at the bottom of the article. The AI spammers have become way less obvious, one even has video. The team still checks every issue.
Right, but the volume was the issue. The cURL team could only work through and verify them so quickly, so the deluge of bug reports just made it impractical for them to dedicate time to sort through it. The idea in getting rid of the bug bounty being that there would be less of an incentive to generate and write a bogus bug report.
Well, another big hint is how the thing answered by addressing a username that wasn't part of the exchange, twice. And then messed up the "@" when they pointed that to it.
If it's even manually copy-pasted, the guy doing that didn't allocate a single braincell to what was being discussed.