←back to thread

FFmpeg to Google: Fund us or stop sending bugs

(thenewstack.io)
1124 points CrankyBear | 2 comments | 11 Nov 25 18:32 UTC | HN request time: 0.411s | source
Show context
chemotaxis ◴[11 Nov 25 19:14 UTC] No.45891486[source]▶
I am fairly confident that this article is largely AI-generated. More generally, the whole site appears to be heavy on AI slop, e.g.: https://thenewstack.io/how-ai-is-pushing-kubernetes-storage-...

And maybe it's fine to have AI-generated articles that summarize Twitter threads for HN, but this is not a good summarization of the discussion that unfolded in the wake of this complaint. For one, it doesn't mention a reply from Google security, which you would think should be pretty relevant here.

replies(1): >>45891720 #
BoredPositron ◴[11 Nov 25 19:31 UTC] No.45891720[source]▶
Like the bug report in question... poetic.
replies(1): >>45895502 #
1. mrob ◴[12 Nov 25 01:53 UTC] No.45895502[source]▶
The bug report in question is obviously written by a human:

https://issuetracker.google.com/issues/440183164?pli=1

It's of excellent quality. They've made things about as easy for the FFmpeg devs as possible without actually fixing the bug, which might entail legal complications they want to avoid.

AI was only used to find the bug.

replies(1): >>45896931 #
2. BoredPositron ◴[12 Nov 25 06:22 UTC] No.45896931[source]▶
"obviously". You have 0 evidence for your comment. Big sleep is credited as reporter.