From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 8DF5D43BEF for ; Mon, 22 Aug 2022 12:52:25 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 8AB7768B98B; Mon, 22 Aug 2022 15:52:22 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id AE9EA68B872 for ; Mon, 22 Aug 2022 15:52:16 +0300 (EEST) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 27MCqGUC013713 for ; Mon, 22 Aug 2022 14:52:16 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id EFF91E0101; Mon, 22 Aug 2022 14:52:15 +0200 (CEST) Date: Mon, 22 Aug 2022 14:52:15 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <612e12d2-4df2-a2fc-5560-7acd93c2fc8f@rothenpieler.org> <20220818143154.GF2088045@pb2> MIME-Version: 1.0 In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Mon, 22 Aug 2022 14:52:16 +0200 (CEST) Subject: Re: [FFmpeg-devel] [PATCH] ipfsgateway: Remove default gateway 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 Content-Type: multipart/mixed; boundary="===============6943506584095566736==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============6943506584095566736== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="zTxUyggbehVBYbwI" Content-Disposition: inline --zTxUyggbehVBYbwI Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Tomas H=E4rdin (12022-08-22): > I'd actually argue that in that case we should link a library that > implements IPFS, not split developer effort by trying to implement it > ourselves. Is FFmpeg meant to be just a convenient set of wrappers for existing libraries, then? If not, what is your criterion to decide when splitting developer effort is worth including a native version in FFmpeg. Regards, --=20 Nicolas George --zTxUyggbehVBYbwI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmMDe/4ACgkQcZVLI8pN xgxfFg/+M8MrjoNoJTys313hRNydvaWe9vPHSCVPQrvVmD9iqrvr1TSe7IDLJgP7 FjPNbuX9yVDxf9FsCeB+gPDt9J/b66YeCuGN6grLrcesd1LU1f5oI2GDAWVHx2f6 FSglyNp/JCPQ3sdoYegZGfYFSgL4o7uM5mxXtxsl8saHa6TEjaR1xsVNrOxUoN5A eU9QUiUqg3YTSkfg7gKBqz0a827UYuMq2ucyfs63ChOn2ifVBEWw54G1NFpf8CcD aTsQFJBCFwd4dZTAal4rNYmHswOlCCuubiInzx55uBKPZ3gD32wijeZmbHz8AYUd Vx3adG1RohMODvm1sweinC02FGv8U9lAwa63pcEDJMPHfcE7UbxmN2FBubV0B7uH 1ZIHcHssYY76TbPhoN9QKT9ICNq7to7AnFG4+4WOWH3859EL+0iSWWR6iZ/Q6xDz E6b2oNcXCNGc4dxb0BFgVN5fQGZWoK+TXR321t3vzI2p83EWzBB+9dM8S/O2O9Xd WcvFzNA5aC8MrER2shdIuUM0MVxyJbKS7EdS27w4IrNp+efW+vklD/g5GUsGmsBR DD3VMF0rA3a58FtCv4Lql+bAFwPZ6Fl5us/mb6KQDMzcJIjZkx5nIBmx3kg4nF/Z L7Y6uXdXa55Zi1BoU2pltU4bRcaaWjUlE4cuSELv3pzj1O8jEgk= =VZLe -----END PGP SIGNATURE----- --zTxUyggbehVBYbwI-- --===============6943506584095566736== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============6943506584095566736==--