From: Michael Niedermayer 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>
Subject: [FFmpeg-devel] Re: FFmpeg "supporters" doxing
Date: Wed, 29 Oct 2025 23:32:58 +0100
Message-ID: <aQKWGkCTgaBRWtDK@neo> (raw)
In-Reply-To: <9322983.Qd6Nj8kapS@basile.remlab.net>
[-- Attachment #1.1: Type: text/plain, Size: 3549 bytes --]
Hi Remi
On Wed, Oct 29, 2025 at 11:31:26PM +0200, Rémi Denis-Courmont via ffmpeg-devel wrote:
> Le keskiviikkona 29. lokakuuta 2025, 22.38.17 Itä-Euroopan normaaliaika
> Michael Niedermayer via ffmpeg-devel a écrit :
> > > When did that happen?
> >
> > Wed, 31 Jan 2024
>
> I can't find it any match in the archives. Besides, that was during the
> previous CC and that CC (of which you were a member and I was not) found no
> issues. I fail to see any sane reason to bring this up again now.
>
> > > Doxxing is the publication of personal info against that person's will -
> > > not quoting some already public info. I seem to recall Kieran *asking*
> > > what actual business stood at a postal address published by NAB (or was
> > > it IBC?) under the name of "FFmpeg".
> > doxxing is about identifying a specific person and exposing or amplifying
> > info in a way that foreseeably invites harassment or harm.
>
> No, that's not what doxxing is. At least according to the wiktionary it is
> either one of:
>
> - To publish personal information of a person without their consent.
> - To reveal the operator of an anonymous online account without their
> consent.
>
> Quoting an already already published public info is not publishing, and more
> importantly, "FFmpeg" is not a person. Kieran did not doxx Thilo. This has
> been explained to you several times.
You talk like you understand legal matters and are refering to wiktionary.
Thilo is in Germany, lets refer to german law:
§ 126a StGB - "Gefährdendes Verbreiten personenbezogener Daten."
The statute criminalizes publicly disseminating another person’s personal data in a manner suitable and intended to expose them (or relatives) to crimes; it covers publicly accessible data (basic offense, up to 2 years) and sets a higher penalty only when the data were not publicly accessible. In short: "public" != "free to blast at scale."
Official Bundestag analysis of § 126a (Wissenschaftliche Dienste).
Explains the law targets "Feindeslisten"/doxxing, explicitly noting that danger can arise even with freely researchable, publicly accessible data-hence criminalization. Also clarifies that publishing data of a single person suffices and what counts as "Verbreiten."
https://www.bundestag.de/resource/blob/867640/846f1ba0205ccdd640c5a8357e655771/strafrechtlicher-Schutz_Feindeslisten_-126a-StGB-data.pdf
> I don't need to remind you that
> continuing to spread those accusations could be construed as libel. At least,
> they validate Vittorio's recent claims that you are carrying a personal
> vendetta against Kieran.
>
> > Even a public work address can fit this
>
> Obviously not. If it is already public then by definition it cannot be doxxing.
see above
> 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.
[...]
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Some Animals are More Equal Than Others. - George Orwell's book Animal Farm
[-- 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-29 22:33 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 [this message]
2025-10-29 23:09 ` Kieran Kunhya via ffmpeg-devel
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=aQKWGkCTgaBRWtDK@neo \
--to=ffmpeg-devel@ffmpeg.org \
--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