From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: ga@ffmpeg.org, Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [POLL][VOTE] Revoke social media delegation
Date: Mon, 27 Oct 2025 12:22:07 +0100
Message-ID: <aP9V35DXFLwqO-ZT@neo> (raw)
In-Reply-To: <cbce0b8c-5fa9-488f-bcfe-e33340286890@lynne.ee>
[-- Attachment #1.1: Type: text/plain, Size: 2165 bytes --]
Hi Lynne
On Sun, Oct 26, 2025 at 05:50:28PM +0100, Lynne via ffmpeg-devel wrote:
[...]
> I looked at the video, and I failed to understand the author's points - he
The authors point is that multiple FFmpeg supporters, who have NOT said bad things
about FFmpeg at all, some who donated to FFmpeg, where pulled into agressive
confrontational arguments by the official FFmpeg account.
Basically the official ffmpeg account is harrasing random supporters. Whenever
the person behind feels an itch to start an argument with someone.
The complaint is not about unconventional or confrontational tone
towards people being incompetent
towards people having spoken badly about ffmpeg or
towards some corporation
its about confrontational action towards ffmpeg supporters, when they
had an issue with vlc or when "ffmpeg" happened to half misread
what they said.
Or when they cause an itch by being associated with C++, type script or other
If vlc wants to confront people who complain about vlc, then vlc should
use their own account for that. Its not our buisness to do that.
Obviously confronting the java script community or c++ or whetevar is just
inappropriate, just why would we, whats the sense of that?
And we should not be confrontational towards our supporters, we simply
should not be. Thats just not appropriate.
If someone wants to do these things, nothing stops them from doing so with their
own personal twitter account. But not the official FFmpeg account
or maybe to litterally quote one part of the video:
"he cares way more about being funny on twitter than representing the project in a good light"
I think this hits one of the core parts of this.
These post are funny (in some sense) and they lead to engagement, but at the same
time they are damaging FFmpegs reputation
I dont think we should trade our reputation for being funny
Also the followers we get from this are shallow, these followers are here for the funny
posts, not for FFmpeg
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
You can kill me, but you cannot change the truth.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-10-27 11:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 15:26 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-26 15:51 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-10-26 17:13 ` Michael Niedermayer via ffmpeg-devel
2025-10-26 17:34 ` Kieran Kunhya via ffmpeg-devel
2025-10-26 17:45 ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-26 16:50 ` Lynne via ffmpeg-devel
2025-10-27 2:22 ` Steven Liu via ffmpeg-devel
2025-10-27 11:22 ` Michael Niedermayer via ffmpeg-devel [this message]
2025-10-26 16:54 ` Tomas Härdin via ffmpeg-devel
2025-10-26 17:51 ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-26 18:18 ` Michael Niedermayer via ffmpeg-devel
2025-10-26 22:34 ` James Almer via ffmpeg-devel
2025-10-27 10:03 ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-27 11:12 ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-26 22:38 ` James Almer via ffmpeg-devel
2025-10-27 1:39 ` Michael Niedermayer via ffmpeg-devel
2025-10-27 11:26 ` Vittorio Giovara via ffmpeg-devel
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=aP9V35DXFLwqO-ZT@neo \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ga@ffmpeg.org \
--cc=michael@niedermayer.cc \
/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