From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Democratization work in progress draft v2 Date: Mon, 3 Feb 2025 20:14:16 +0100 Message-ID: <20250203191416.GA4991@pb2> (raw) In-Reply-To: <45c37d06-f49b-42ff-a841-64cfaa513af4@gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1773 bytes --] Hi On Sun, Feb 02, 2025 at 03:14:58PM -0300, James Almer wrote: > On 2/1/2025 6:53 PM, Michael Niedermayer wrote: > > Hi James > > > > On Sat, Feb 01, 2025 at 10:30:21AM -0300, James Almer wrote: > > > On 1/31/2025 9:49 PM, Michael Niedermayer wrote: [...] > , the text points this out in a mocking/ironic way. > > If you want me to reword this in a dry formal way, i can submit such a patch? > > > > If not, how do you suggest we move forward here ? > > We can replace the GA by a system that is not vulnerable > > I ask again, do you have any reason other than an hypothetical scenario to > think the GA is vulnerable? Isnt every vulnerability that was reported to us a "hypothetical" scenario ? > Or can you mention a point during the last five > years where any such a vulnerability was taken advantage of? Lets assume we have 2 projects in one the vulnerability was taken advantage of while in the other it was not. How would you tell them apart ? in both these universes 11 people join over the course of a year In one universe these are all just random new developers. In the other they are payed to gain vote power and control. If you list their names from both of these universes, you will notice a shocking detail in both universes, its the same people, just in one they where payed and in the other they joined for their own reasons. I hope you see that we cannot detect this Then how would "not detecting" this, mean anything ? thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Many things microsoft did are stupid, but not doing something just because microsoft did it is even more stupid. If everything ms did were stupid they would be bankrupt already. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2025-02-03 19:14 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-01-29 20:33 Michael Niedermayer 2025-01-29 21:39 ` Leo Izen 2025-01-29 21:47 ` Nicolas George 2025-01-29 21:48 ` Soft Works 2025-01-30 6:38 ` Vittorio Giovara 2025-01-29 23:43 ` Niklas Haas 2025-01-30 18:04 ` Michael Niedermayer 2025-01-31 14:36 ` Nicolas George 2025-01-31 14:58 ` Nicolas George 2025-01-31 15:44 ` James Almer 2025-01-31 16:01 ` Soft Works 2025-02-02 2:25 ` Leo Izen 2025-02-02 3:37 ` Soft Works 2025-02-02 7:29 ` Vittorio Giovara 2025-02-01 0:49 ` Michael Niedermayer 2025-02-01 6:45 ` Zhao Zhili 2025-02-01 13:21 ` Ronald S. Bultje 2025-02-01 14:30 ` Vittorio Giovara 2025-02-01 14:11 ` Jean-Baptiste Kempf 2025-02-01 14:31 ` Vittorio Giovara 2025-02-02 11:34 ` Michael Niedermayer 2025-02-01 13:30 ` James Almer 2025-02-01 21:53 ` Michael Niedermayer 2025-02-02 18:14 ` James Almer 2025-02-03 18:08 ` Michael Niedermayer 2025-02-03 18:16 ` Vittorio Giovara 2025-02-03 19:14 ` Michael Niedermayer [this message] 2025-02-03 20:45 ` Nicolas George 2025-02-03 2:29 ` Ronald S. Bultje 2025-02-01 22:27 ` Michael Niedermayer 2025-02-01 22:29 ` Kieran Kunhya via ffmpeg-devel 2025-02-02 21:35 ` James Almer 2025-01-30 6:41 ` Vittorio Giovara 2025-02-01 20:44 ` Nicolas George 2025-02-02 0:01 ` Michael Niedermayer
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=20250203191416.GA4991@pb2 \ --to=michael@niedermayer.cc \ --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