From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 71E7D4C292 for ; Thu, 31 Jul 2025 11:26:18 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id BC7D668CCE4; Thu, 31 Jul 2025 14:26:13 +0300 (EEST) Received: from haasn.dev (haasn.dev [78.46.187.166]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id A619168C9FF; Thu, 31 Jul 2025 14:26:02 +0300 (EEST) Received: from haasn.dev (unknown [10.30.1.1]) by haasn.dev (Postfix) with UTF8SMTP id 47D4D4079C; Thu, 31 Jul 2025 13:26:02 +0200 (CEST) Date: Thu, 31 Jul 2025 13:26:02 +0200 Message-ID: <20250731132602.GB125056@haasn.xyz> From: Niklas Haas To: FFmpeg development discussions and patches In-Reply-To: References: MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [FFmpeg-devel] [IMPORTANT] AI written TLS Code in WHIP patch X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Cc: tc@ffmpeg.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Tue, 29 Jul 2025 21:02:53 +0100 Kieran Kunhya 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. Speaking on my own behalf (not constituting a TC opinion), I think that in this specific case, a revert is not needed as the code is already marked experimental, and other people have cleaned it up since its initial state. Reverting all that would at this point be more trouble than it's worth. I'll withhold my opinion on AI contributions in general for the time being. > > 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".