From: "Rémi Denis-Courmont 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>,
"Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: FFmpeg "supporters" doxing
Date: Thu, 30 Oct 2025 09:50:19 +0200
Message-ID: <A64A7145-D509-4855-800E-43F8585C1C48@remlab.net> (raw)
In-Reply-To: <aQKWGkCTgaBRWtDK@neo>
Hi,
Le 30 octobre 2025 00:32:58 GMT+02:00, Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> a écrit :
>You talk like you understand legal matters and are refering to wiktionary.
>Thilo is in Germany, lets refer to german law:
Pretty sure German law doesn't define the English term "doxxing". And again, maybe the conference organisation, not Kieran, violated German law, but:
1) That does not justify knowingly repeated slander against another member of the community (or really anyone).
2) The conference is probably outside German jurisdiction anyway.
3) In all likelihood, Thilo granted permission for the conference to publish the address in the fineprint of the exhibitor contractual terms.
4) If it was Thilo's *office* address, it's likely even public information from the trade register.
>> Obviously not. If it is already public then by definition it cannot be doxxing.
>
>see above
I don't see aything 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.
"Who" implies that it was a **question**. If someone committed "doxxing" under either of the generally accepted definitions, that's whoever **answered** that it was Thilo.
>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".
Again, you were a member of the CC and I was not at the time, so whatever. I doubt that the other members of the CC at the time will appreciate those comments though.
The current CC has no authority over stuff that was handled by a previous CC. A contrario, the current CC already took actions publicly against Kieran in other matters earlier *this* year.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-10-30 7:51 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
2025-10-30 7:50 ` Rémi Denis-Courmont via ffmpeg-devel [this message]
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=A64A7145-D509-4855-800E-43F8585C1C48@remlab.net \
--to=ffmpeg-devel@ffmpeg.org \
--cc=marth64@proxyid.net \
--cc=michael@niedermayer.cc \
--cc=remi@remlab.net \
/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