From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [IMPORTANT] AI written TLS Code in WHIP patch Date: Tue, 29 Jul 2025 17:11:15 -0300 Message-ID: <d3b94a93-77ab-47e1-ad46-778130693f7e@gmail.com> (raw) In-Reply-To: <CABGuwEmoDQix1u4B2KJmd3BjhZLoSzmxNTqEg8=GmHt2WjFcQA@mail.gmail.com> [-- Attachment #1.1.1: Type: text/plain, Size: 1470 bytes --] On 7/29/2025 5:02 PM, Kieran Kunhya via ffmpeg-devel wrote: > Hello, > > It seem there is strong evidence that AI wrote TLS code as part of the > WHIP patch. It goes without saying why this is bad. Further discussion > here: > https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20053 > > This patch was pushed without ML review. > > I think this code should be removed before the FFmpeg release. I > include TC in this email for that reason. The UTF8 dashes are not so much an indication of LLM output but one that it was written with an unusual locale, I'd say. As for the allegations that the code was seemingly written with one objective in mind, sure, that can be what an LLM does based on prompts, but also what a person does. It would not be the first time someone writes code without thinking of it having to work generically (The amount of API that was made for a single, very specific usecase that had to then be replaced by a more general one is not small). That said, I agree the changes did look weird in places, so I'm not against reverting them in the release/8.0 branch so we have more time to properly audit it. > > Regards, > Kieran Kunhya > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 495 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-07-29 20:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-29 20:02 Kieran Kunhya via ffmpeg-devel 2025-07-29 20:11 ` James Almer [this message] 2025-07-29 20:56 ` Kacper Michajlow 2025-07-29 22:39 ` James Almer 2025-07-29 22:59 ` Timo Rothenpieler 2025-07-30 0:42 ` Jack Lau
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=d3b94a93-77ab-47e1-ad46-778130693f7e@gmail.com \ --to=jamrial@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git