From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
Kieran Kunhya <kieran618@googlemail.com>
Subject: [FFmpeg-devel] Re: [POLL][VOTE] Sponsors & Funding
Date: Sat, 4 Oct 2025 08:09:15 +0900
Message-ID: <CABGuwE=kfVg6oH-86bySaTMmYFHM=unf3f3vWpmM4sDAQDDXYA@mail.gmail.com> (raw)
In-Reply-To: <aOBTpoOj_oqQYSTN@neo>
"Yes"
> We can say, that this extra money will be used to hire people,
> and for maintaince and development.
> A Company that depends on FFmpeg has a reason to spend 100k/y here, its
> tiny for
> many companies, and they make MUCH larger sums with their buisness
> depending on
> FFmpeg.
>
But what happens when you spread conspiracy theories about said companies
as you have with (included but not limited to), Vimeo and FFlabs?
Do you Michael Niedermayer promise to respect the wishes of the GA and not
spread conspiracy theories?
Or does this project remain an conspiracy theory / paranoia discussion site
that happens to develop multimedia?
Kieran
_______________________________________________
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-03 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 12:55 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-02 16:28 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-10-03 22:52 ` Michael Niedermayer via ffmpeg-devel
2025-10-03 23:09 ` Kieran Kunhya via ffmpeg-devel [this message]
2025-10-05 22:10 ` Michael Niedermayer via ffmpeg-devel
2025-10-09 15:00 ` Michael Niedermayer via ffmpeg-devel
2025-10-10 14:08 ` Kieran Kunhya 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='CABGuwE=kfVg6oH-86bySaTMmYFHM=unf3f3vWpmM4sDAQDDXYA@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
--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 http://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/ http://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