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 100E443DE1 for ; Fri, 12 Aug 2022 14:55:23 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 64EF368B8D2; Fri, 12 Aug 2022 17:55:21 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id D067568B5B7 for ; Fri, 12 Aug 2022 17:55:14 +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 27CEtDKo022671 for ; Fri, 12 Aug 2022 16:55:13 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id 890FBE0101; Fri, 12 Aug 2022 16:55:13 +0200 (CEST) Date: Fri, 12 Aug 2022 16:55:13 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <20220810222708.186270-1-derek.buitenhuis@gmail.com> <612e12d2-4df2-a2fc-5560-7acd93c2fc8f@rothenpieler.org> <20220811201834.GE2088045@pb2> <7ce22e69-d0ad-16b7-52c6-0a447ce05be2@rothenpieler.org> 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]); Fri, 12 Aug 2022 16:55:13 +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="===============2385876267421761685==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2385876267421761685== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ObozY9g71xFB6fWW" Content-Disposition: inline --ObozY9g71xFB6fWW Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Derek Buitenhuis (12022-08-11): > I agree... we should never send a users data through *any* service they > haven't explicitly asked for. Ever. Regardless of who runs it and who > is deemed "trustworthy". Absolutely. And Kieran's simile with DNS is very good. It is not just a question of whether the gateway might turn evil, there are also concerns of privacy. > > The patch wasn't on my radar at all. I had assumed it was actually=20 > > implementing IPFS in some fashion. > Yes, I had assumed the same too, and thus wasn't following the sets > at all. >=20 > As it exists right now though, I don't really see why lavf needs what > amounts to a URL builder for a service as a "protocol" - this totally > the wrong layer to do that at... I also assumed it was a native implementation. If it is just a matter of translating =E2=80=9Cipfs://whatever=E2=80=9D into =E2=80=9Chttps://gateway= /wHaTeVeR=E2=80=9D, a perl script in tools/ would be a reasonable expedient. Native implementations are a huge part of what made FFmpeg great: you build from source, without a shit-ton of extra libraries that might not be packaged or recent enough on long-term distributions, and you get support for most codecs, formats and protocols in the world. Unfortunately, work on implementing native versions of codecs and protocols seems to have gotten out of fashion. For protocols, I can blame the lack of framework: our pedestrian read/write blocking API is not adapted to modern protocols that require asynchronous operation. I had the project of building a new framework for networking and protocols; in fact I have a large part of how I want to make it work in the back of my mind already. But considering the shortsightedness of the leadership of the project these days about framework that is not an obvious incremental enhancement directly related to existing code, I do not expect to invest more time into it any time soon. The same goes for most API enhancement I had promised over the years. Too bad. Regards, --=20 Nicolas George --ObozY9g71xFB6fWW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmL2ac8ACgkQcZVLI8pN xgx+kA//Y9UkpTWChj9yABE0Vr7yjkHwKD/AN8bAjgNc+LUh0y2yJivFVOA7a5wS khhG7cPL/e4x0Rb+tG0BMfcPBPlaQKHyLmqbukBc96tCpTPBZzLQbbSLHWKD14w0 /2gwtAdnLV9amFXpgdmnAW64k5O+vcXNzYrOfKJL9FDLa/byKH2bwlyFijtWNt7D K/mgLQb6L4eF9PC6RIpYoOsxOvLbd74SLUZeGseCdaT5CHMOUjhzJxTcAcVJf/pG /9AYqLEg7o27518WOSQ4I5FoCq49fXHXSvy+iU34b1D5IeVn8CPZUual3GLryA5K fsdhEVVXtQBFdWQurlEADehHtDWA3yzWM+FAnD+O8IUaiO4mAbeqp/UnJEO/CR33 dk7HVjr0d1fhqfwEJ1DzNJGIQTMJzyMWm27eXXs9DkZ6EnyC/BXrHvP3OeEiDFQ1 trp+bkr/Az0Yy3m1BQAsuX2gVc102iGq3wudxTCxXnr8f9R9bwX51UYrn/XXEN5p 8fJb2+uhVGwpJJgi+VWUktQVde3fpmzgwwQysWSP6QZZyZcNVyI7xEdSgrBgRXlB sHVpGrAwCqV3quKmUxVHAfp7eMllkLfc5nmOQOZs7ArGGXrp0GfASDYdrFtJ0i2o 33FW94gBoL5yVEc++MZjaItJXFA1Cz8XQHJth59/du5dE3xCF/E= =1d+P -----END PGP SIGNATURE----- --ObozY9g71xFB6fWW-- --===============2385876267421761685== 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". --===============2385876267421761685==--