Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: FFmpeg "supporters" doxing
Date: Wed, 29 Oct 2025 21:38:17 +0100
Message-ID: <aQJ7OTj4vFCojJH3@neo> (raw)
In-Reply-To: <14303C68-C07E-4A1B-8F17-D460F729E44F@remlab.net>


[-- Attachment #1.1: Type: text/plain, Size: 2177 bytes --]

Hi Remi

On Wed, Oct 29, 2025 at 07:55:09PM +0200, Rémi Denis-Courmont via ffmpeg-devel wrote:
> 
> 
> Le 29 octobre 2025 19:09:15 GMT+02:00, Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> a écrit :
> >Does this also apply to the case where kieran doxxed thilo ?
> 

> When did that happen?

Wed, 31 Jan 2024


> 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.
Even a public work address can fit this
Especially with hostile framing.


> 
> Then someone else claimed it to be Thilo's home address. I could recall wrong and in any case, I don't recall for sure who did that. But indeed, unless it was Thilo himself, then we could consider that that third person was doxxing Thilo.

Thilo announced the NAB 2024 booth:
    https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-November/316474.html
    Date: Wed, 1 Nov 2023 21:37:04 +0100
    Subject: [FFmpeg-devel] FFmpeg at NAB 2024

Kieran participated in that thread on:
    Sun Nov 19 16:26:22 EET 2023
    https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-November/317199.html
    This and surrounding mails also question a range of things in a hostile tone

So Kieran knew that Thilo was associated with the booth. And there was a prior set
of critique pointing to thilo.
Subsequently posting the address and asking "Who does this address belong to?"
is IMO Doxxing

also, he asked "Who" not "which company"


> 
> As for Kieran's quote, Thilo is welcome to thank Kieran for the notice and complain to the conference organisation for their lackluster privacy.

Kieran posted the address in public. That was not neccessary to inform Thilo about it

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Why not whip the teacher when the pupil misbehaves? -- Diogenes of Sinope

[-- 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

  reply	other threads:[~2025-10-29 20:39 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 [this message]
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
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=aQJ7OTj4vFCojJH3@neo \
    --to=ffmpeg-devel@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