From: Michael Koch <astroelectronic@t-online.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] trac spam
Date: Sun, 3 Dec 2023 13:06:48 +0100
Message-ID: <28f42b61-03c7-3e40-eefe-320a6f8e9a33@t-online.de> (raw)
In-Reply-To: <439b45fe-90cf-446b-abec-8f5126ce1f21@frankplowman.com>
> Perhaps the regex search is performed on the rendered text as opposed to
> the source text? Taking the spam comment on #2104 as an example, the
> spammer appears to be using the `[<URI> <Display Text>]` or
> `[[<URI>|<Display Text>]]` markup, therefore `http` does not appear in
> the rendered text.
But on the other hand, the regex filter did match two times in the spam comment in ticket 2776.
Why?
This comment was only accepted after the spammer solved the captcha.
Michael
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-12-03 12:06 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 17:28 Michael Koch
2023-10-19 9:36 ` Michael Koch
2023-10-19 13:50 ` Michael Koch
2023-10-19 14:21 ` Michael Koch
2023-10-19 16:40 ` Michael Niedermayer
2023-10-19 17:05 ` Michael Koch
2023-10-19 17:34 ` Michael Niedermayer
2023-10-19 17:49 ` Michael Koch
2023-10-19 18:18 ` Michael Niedermayer
2023-10-19 19:05 ` Michael Koch
2023-10-19 19:39 ` epirat07
2023-10-20 13:45 ` Michael Niedermayer
2023-10-20 17:53 ` Michael Koch
[not found] ` <01C7FB4B-894A-43A5-B15D-3B5ECCD046D7@cosmin.at>
2023-10-20 18:24 ` Cosmin Stejerean via ffmpeg-devel
2023-10-21 21:45 ` Michael Niedermayer
2023-10-19 19:45 ` Michael Koch
2023-10-19 17:43 ` Michael Niedermayer
2023-10-26 14:37 ` Michael Koch
2023-10-26 21:01 ` Michael Niedermayer
2023-10-27 12:44 ` Michael Koch
2023-10-27 17:53 ` Michael Niedermayer
2023-11-06 9:06 ` Anton Khirnov
2023-11-06 16:09 ` Michael Niedermayer
2023-11-06 8:25 ` Michael Koch
2023-11-06 15:59 ` Michael Niedermayer
2023-11-06 9:03 ` Michael Koch
2023-11-06 15:57 ` Michael Niedermayer
2023-12-03 8:39 ` Michael Koch
2023-12-03 8:49 ` Michael Koch
2023-12-03 9:36 ` Masaru Nomiya
2023-12-03 9:57 ` Michael Koch
2023-12-03 10:23 ` Masaru Nomiya
2023-12-03 10:41 ` Michael Koch
2023-12-03 11:44 ` Frank Plowman
2023-12-03 12:06 ` Michael Koch [this message]
2023-12-03 23:04 ` Michael Niedermayer
-- strict thread matches above, loose matches on Subject: below --
2023-09-20 11:46 [FFmpeg-devel] TRAC Spam Michael Koch
2023-09-20 12:30 ` Paul B Mahol
2023-09-20 14:33 ` Michael Niedermayer
2023-09-20 15:28 ` Paul B Mahol
2023-09-20 17:05 ` Michael Niedermayer
2023-09-21 6:52 ` Michael Koch
2023-09-21 16:48 ` Michael Niedermayer
2023-09-22 8:00 ` Michael Koch
2023-09-22 8:58 ` Michael Niedermayer
2023-09-22 8:39 ` Michael Koch
2023-09-22 9:03 ` Diederick C. Niehorster
2023-09-22 9:14 ` Michael Koch
2023-09-22 10:49 ` Hendrik Leppkes
2023-09-22 11:10 ` Michael Koch
2023-09-21 16:49 ` Michael Niedermayer
2023-09-20 14:30 ` Michael Niedermayer
2023-09-19 5:44 Michael Koch
2023-09-19 17:49 ` Michael Niedermayer
2023-09-10 9:20 [FFmpeg-devel] Trac spam Michael Koch
2023-09-10 22:16 ` Michael Niedermayer
2023-09-11 12:20 ` Michael Koch
2023-09-11 23:11 ` Michael Niedermayer
2023-09-12 0:18 ` Michael Niedermayer
2023-09-12 5:03 ` Michael Koch
2023-09-12 22:09 ` Michael Niedermayer
2023-09-07 4:20 Michael Koch
2023-09-07 17:59 ` Michael Niedermayer
2023-09-03 12:39 Michael Koch
2023-09-03 16:12 ` Michael Niedermayer
2023-04-24 20:23 [FFmpeg-devel] trac spam Michael Niedermayer
2023-04-25 12:59 ` Thilo Borgmann
2023-05-15 6:02 ` Michael Koch
2023-05-16 17:54 ` Michael Niedermayer
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=28f42b61-03c7-3e40-eefe-320a6f8e9a33@t-online.de \
--to=astroelectronic@t-online.de \
--cc=ffmpeg-devel@ffmpeg.org \
/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