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 8104943AC7 for ; Thu, 11 Aug 2022 17:22:21 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 6C34268B934; Thu, 11 Aug 2022 20:22:18 +0300 (EEST) Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id C593968B7F8 for ; Thu, 11 Aug 2022 20:22:11 +0300 (EEST) Received: by mail-ej1-f54.google.com with SMTP id dc19so34582201ejb.12 for ; Thu, 11 Aug 2022 10:22:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc; bh=UirFzfT6f5C9ztK6vC/MZB3X6KbvGxwMM9CkkSwlNo4=; b=Sy+XEvhdvR9CP5EZFYtvyv4sKFbJu0ACfmfsISQihgLQhUnHmsFGXA4ZVmETtRTz31 RaaEWduCVji6qd2suYb2vghaiEB62g9+uzVCkXrnMEo9JuyVCfDhIRkBEAzCnMsX5Rbb mUrVr2/pEHrFKgq8COPwYLIoPxXLtS2yN0ph7nsoQD11aSpTCdNGKLC/ncb5qFa4wn7t 3tnawAzOMy4WsMut9hwsw7g99+oDrIsgQT9fJixFZOj/tqBKKMyWYgccxqdPaTE+k3lI Zh9fkWyX1Hk2JRirhUE7xcNNOnCnPCv4mYYMGD+fRWdiEIqBeAqGB5THnC1IVzwWFw7R PLkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc; bh=UirFzfT6f5C9ztK6vC/MZB3X6KbvGxwMM9CkkSwlNo4=; b=zyYKtthNuqMXfy6dfI5++2zq8nLBytRXmyTt2niKQTs/oupX3ryVpm1gQZNRN8Vq/d zM9gc49UutxbVCcZy9/pVlpm13ud/GZWGEIa2q9M4MJPB5qStfvbaf9wZ9i7roZELLlV Y5/UuVR7QkYXR0BD5NPdikUu/GDHPpblns2iUz7E+0wYt/vHk86HS0vo5KiCBr2E8wE8 ov9Xlo3zvL229iLGBWAkGzZ+1heE7ll5Xs0L0skodJMJRdDJbZlVHuuD1K5vBCNTXlaI QKyjQ8XD2ucD6FnIRmP/ZnLrMeh8kiV9rP5HTqveWPMRMB6e6EzaanAsqxNI7j6Kqbz2 mULA== X-Gm-Message-State: ACgBeo19cdPIDHJidjS4BAgsrgU+CEQhorF9jEZyFN9Mz7rgmm1xlzxx xaCy+Mar8c10NeL4WRr16qyxixT32x3sKMO2y1+uCcysT+M= X-Google-Smtp-Source: AA6agR4juTxMSqSARv9E498ua46yu19AOzGi984Ttc/BDwy3gWeK+yKTRZV6UVCOjHDtVQmM8u1V2oalEEwHD4GK75Y= X-Received: by 2002:a17:907:60c7:b0:731:2be4:f72d with SMTP id hv7-20020a17090760c700b007312be4f72dmr35862ejc.639.1660238530914; Thu, 11 Aug 2022 10:22:10 -0700 (PDT) MIME-Version: 1.0 References: <20220810222708.186270-1-derek.buitenhuis@gmail.com> <612e12d2-4df2-a2fc-5560-7acd93c2fc8f@rothenpieler.org> In-Reply-To: <612e12d2-4df2-a2fc-5560-7acd93c2fc8f@rothenpieler.org> From: Mark Gaiser Date: Thu, 11 Aug 2022 19:21:57 +0200 Message-ID: To: FFmpeg development discussions and patches X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: 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 Thu, Aug 11, 2022 at 6:49 PM Timo Rothenpieler wrote: > On 11.08.2022 18:26, Mark Gaiser wrote: > > Hi all, > > > > On the IPFS side we do have a solution for that with CAR files, you can > > read more about that here [1]. > > Within the scope of this ipfs gateway protocol handler there isn't a > > solution yet to use CAR files, it is on our radar but still in the > > discussion phase. > > > > On the cURL side we had this same discussion with 2 possible solutions > [2]. > > For completeness, i'll list them here in full too: > > > > 1. An error message that gives no example but instead points the user to > > documentation on how to get it working. > > === cURL example > > $ curl ipfs://bafkreicysg23kiwv34eg2d7qweipxwosdo2py4ldv42nbauguluen5v6am > > Error: local gateway not found and/or IPFS_GATEWAY is not set > > Learn how to run one: https://docs.ipfs.tech/install/command-line/ > > === > > > > 2. An error message that makes the user aware of IPFS and provides a > > solution to get it working immediately. > > === cURL example > > $ curl ipfs://bafkreicysg23kiwv34eg2d7qweipxwosdo2py4ldv42nbauguluen5v6am > > Error: local gateway not found and/or IPFS_GATEWAY is not set. > > Try: IPFS_GATEWAY=https://ipfs.io > > or run your own: https://docs.ipfs.tech/install/command-line/ > > === > > > > Within the cURL implementation we're going for point 1. > > The same idea can very well apply to ffmpeg too. Different texts that > match > > the different context, but in the same spirit. > > > > Now ffmpeg is a bit different here. First and foremost because it > predates > > the curl. > > But also because the default fallback gateway was an explicitly requested > > feature from the ffmpeg side to give an "it always works" feeling. > > ffmpeg therefore has a fourth option: Do nothing and keep it as-is. > > I'm not sure who requested that, but I doubt "tunnel all user traffic > through some random third parties server" was the idea there. > Here's the conversation requesting this very feature: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-March/293835.html > > Releases with that hardcoded server in will be in distributions for > years, potentially over a decade long. > Nobody can guarantee that it doesn't turn malicious in the future. > And nobody can fully guarantee what the owner does with all the data today. > > This is simply unacceptable and it has to be fixed ASAP. > The approach taken by this patch seems the correct way to deal with it > to me. > It prints a message informing the user on what to do, akin to what curl > seems to do. > _______________________________________________ > 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". > _______________________________________________ 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".