From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] ipfsgateway: Remove default gateway
Date: Thu, 11 Aug 2022 20:18:11 +0100
Message-ID: <bccf6486-3db4-d4c5-3cb7-3443feb07be3@gmail.com> (raw)
In-Reply-To: <CAPd6JnEhWXSj9C_NOBLGcM9rMgRK_xH4cxpXGAdi=SYm4BqUZA@mail.gmail.com>
On 8/11/2022 6:56 PM, Mark Gaiser wrote:
> This is just your - valued! - opinion, but still just 1. I insist on
> waiting to hear from Michael to hear a decision on this, mainly because he
> was quite persistent in asking for this feature to begin with.
> The risks were clear and - somewhat - mentioned in the post I linked to
> before yet the decision was still to proceed.
This is a bigger issue than a single person's opinion - it's just plainly an
unacceptable risk. I totally agree with Timo here.
'Just works' isn't an acceptbale reason to ship a hard coded third party
sever as part of a widely used FOS library and tool.
I admit I was large absent from the original (many) rounds or review,
but I'm kind of surprised it was merged as-is, to be honest. Frankly either
it should've been merged as "batteries not included", or should have been
a whole IPFS implementation.
However, regardless of how this came to be (whether reasonable or not), this
should be removed.
-Derek
_______________________________________________
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:[~2022-08-11 19:18 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 22:27 Derek Buitenhuis
2022-08-11 12:08 ` Timo Rothenpieler
2022-08-11 16:26 ` Mark Gaiser
2022-08-11 16:49 ` Timo Rothenpieler
2022-08-11 17:21 ` Mark Gaiser
2022-08-11 17:35 ` Timo Rothenpieler
2022-08-11 17:56 ` Mark Gaiser
2022-08-11 19:18 ` Derek Buitenhuis [this message]
2022-08-11 20:18 ` Michael Niedermayer
2022-08-11 22:03 ` Timo Rothenpieler
2022-08-11 22:51 ` Derek Buitenhuis
2022-08-12 13:43 ` Mark Gaiser
2022-08-12 14:22 ` Vittorio Giovara
2022-08-12 14:30 ` Kieran Kunhya
2022-08-12 14:34 ` Mark Gaiser
2022-08-12 14:45 ` Kieran Kunhya
2022-08-12 14:48 ` Derek Buitenhuis
2022-08-12 14:50 ` Kieran Kunhya
2022-08-12 14:55 ` Nicolas George
2022-08-12 15:05 ` Michael Niedermayer
2022-08-12 17:01 ` Nicolas George
2022-08-12 17:18 ` Michael Niedermayer
2022-08-12 17:21 ` Timo Rothenpieler
2022-08-13 16:29 ` Michael Niedermayer
2022-08-13 19:06 ` Timo Rothenpieler
2022-08-14 18:00 ` Michael Niedermayer
2022-08-15 14:09 ` Nicolas George
2022-08-15 14:27 ` Jean-Baptiste Kempf
2022-08-17 15:03 ` Tomas Härdin
2022-08-18 14:31 ` Michael Niedermayer
2022-08-19 9:15 ` Tomas Härdin
2022-08-19 12:52 ` Mark Gaiser
2022-08-22 9:12 ` Tomas Härdin
2022-08-22 12:52 ` Nicolas George
2022-08-23 12:53 ` Ronald S. Bultje
2022-08-23 12:55 ` Nicolas George
2022-08-24 16:35 ` Tomas Härdin
2022-08-24 20:54 ` Michael Niedermayer
2022-08-27 7:05 ` Tomas Härdin
2022-08-28 14:14 ` Michael Niedermayer
2022-08-24 21:03 ` Michael Niedermayer
2022-08-24 21:18 ` Kieran Kunhya
2022-08-25 13:57 ` Michael Niedermayer
2022-08-25 14:41 ` Kieran Kunhya
2022-08-27 7:29 ` Tomas Härdin
2022-08-27 7:53 ` Paul B Mahol
2022-08-27 11:30 ` Tomas Härdin
2022-08-27 17:34 ` Baptiste Coudurier
2022-08-28 11:49 ` Tomas Härdin
2022-08-15 17:53 ` Michael Niedermayer
2022-08-15 19:35 ` Derek Buitenhuis
2022-08-15 19:37 ` James Almer
2022-08-15 21:47 ` Michael Niedermayer
2022-08-15 21:57 ` Nicolas George
2022-08-15 23:53 ` Mark Gaiser
2022-08-16 14:46 ` Michael Niedermayer
2022-08-14 13:24 thelostone123
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=bccf6486-3db4-d4c5-3cb7-3443feb07be3@gmail.com \
--to=derek.buitenhuis@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