←back to thread

1124 points CrankyBear | 1 comments | | HN request time: 0s | source
Show context
ganelonhb ◴[] No.45891485[source]
Not too fond of maintainers getting too uppity about this stuff. I get that it can be frustrating to receive bug report after bug report from people who are unwilling or unable to contribute to the code base, or at the very least to donate to the team.

But the way I see it, a bug report is a bug report, no matter how small or big the bug or the team, it should be addressed.

I don’t know, I’m not exactly a pillar of the FOSS community with weight behind my words.

replies(4): >>45891536 #>>45891550 #>>45891599 #>>45900858 #
calcifer ◴[] No.45891536[source]
> it can be frustrating to receive bug report after bug report from people

As the article states, these are AI-generated bug reports. So it's a trillion-dollar company throwing AI slop over the wall and demanding a 90-day turn around from unpaid volunteers.

replies(1): >>45891559 #
ikiris ◴[] No.45891559[source]
Do you have evidence of ai slop, or are you just spreading fud? The linked bug was acknowledged as real.
replies(2): >>45891582 #>>45891632 #
ehutch79 ◴[] No.45891632[source]
google literally tells them it's an ai generated report
replies(1): >>45891654 #
ikiris ◴[] No.45891654[source]
That is not the definition of slop.
replies(1): >>45891837 #
blibble ◴[] No.45891837[source]
if it's unwanted then it is

and the ffmpeg maintainers say it's not wanted

so it's slop

replies(1): >>45892384 #
1. iscoelho ◴[] No.45892384[source]
It’s a reproducible use-after-free in a codec that ships by default with most desktop and server distributions. It can be leveraged in an exploit chain to compromise a system.

I'm not a Google fan, but if the maintainers are unable to understand that, I welcome a fork.