From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Yalda <marth64@proxyid.net>,
Michael Niedermayer <michael@niedermayer.cc>,
Kieran Kunhya <kieran618@googlemail.com>
Subject: [FFmpeg-devel] Re: FFmpeg "supporters" doxing
Date: Wed, 29 Oct 2025 23:09:05 +0000
Message-ID: <CABGuwE=HF14O2Du9TvZdAeFkcEaUopZaejXFatfZ+gtbnidAEQ@mail.gmail.com> (raw)
In-Reply-To: <aQKWGkCTgaBRWtDK@neo>
>
>
> > And again, the more important aspect here is that Kieran was *asking*,
> not
> > publishing, what *business*, not person, sits at a given already
> published
>
> The litteral text from kieran was
>
> "Who does this address belong to?"
> and "who" normally implies a person.
>
> All above said, if the CC refuses to act on this, obviously that proofs my
> point
> which was that "the CC is not acting on this". May that be, because the
> data was
> there in form of a question, or it was a too long ago, or whatever.
>
> While there seem to be action in other cases of doxxing.
>
"Who" can apply to a company in English. To use Grok's explanation:
""Who" in English is traditionally used for people, but in modern
usage—especially in questions about ownership, registration, or
association—it is commonly extended to organizations, businesses, or legal
entities."
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-29 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANJ8oft9csg8HueRKu+FqufgL6HA5a_0cMNFqXkhbo7CHL8gwQ@mail.gmail.com>
2025-10-28 7:48 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-10-28 10:01 ` [FFmpeg-devel] " Jean-Baptiste Kempf via ffmpeg-devel
2025-10-29 17:09 ` Michael Niedermayer via ffmpeg-devel
2025-10-29 17:55 ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-29 20:38 ` Michael Niedermayer via ffmpeg-devel
2025-10-29 20:59 ` Kieran Kunhya via ffmpeg-devel
2025-10-29 21:31 ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-29 22:32 ` Michael Niedermayer via ffmpeg-devel
2025-10-29 23:09 ` Kieran Kunhya via ffmpeg-devel [this message]
2025-10-30 7:50 ` Rémi Denis-Courmont 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=HF14O2Du9TvZdAeFkcEaUopZaejXFatfZ+gtbnidAEQ@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
--cc=marth64@proxyid.net \
--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