Painful to read
Comment on Death by a thousand slops
brsrklf@jlai.lu 1 week ago
The great thing about asking gen AI to look for problems, is that it’s so helpful it will create new ones for you.
Like arguing for hours that if you were to remove safeguards from your code, it would become unsafe.
embed_me@programming.dev 1 week ago
lemmydividebyzero@reddthat.com 1 week ago
Luckily, the word “Centainly” 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.
TheBlackLounge@lemmy.zip 1 week ago
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.
T156@lemmy.world 1 week ago
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.
They didn’t have the manpower to keep up.
TheBlackLounge@lemmy.zip 1 week ago
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.
brsrklf@jlai.lu 1 week ago
Well, another big hint is how the thing answered by addressing a username that wasn’t part of the exchange, twice.
If it’s even manually copy-pasted, the guy doing that didn’t allocate a single braincell to what was being discussed.