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 <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] statictrac, trac and caching
Date: Sun, 15 Jun 2025 18:28:31 +0200
Message-ID: <20250615162831.GX29660@pb2> (raw)
In-Reply-To: <981c3a86-57de-4626-90a8-b236a6987216@gmail.com>


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

Hi

On Sun, Jun 15, 2025 at 11:53:28AM -0300, James Almer wrote:
> On 6/15/2025 10:35 AM, Michael Niedermayer wrote:
> > Hi all
> > 
> > As it seems someone figured out how to make AI solve anubis, which made trac
> > rather slow due to the DDOS from 100 different IPs, which eventually
> > we had to block.
> > (maybe timo has time to write an incident report?)
> > 
> > Some questions
> > * does someone know how to make trac use/set cache-control headers
> >      (this would simply and plainly reduce load on trac for pages that dont change
> >       but has to play along correctly with user sessions and all that)
> > 
> > * should we make a static copy of the whole trac so the
> >      AI users, vibe coders, AI data analyists, and AI bot trainers can actually
> >      use trac while everyone else also can use it ?
> >      that static copy would then get updated ... i dont know, maybe once a week?
> >      side effect, even humans would have a "instant responce but older trac" too
> 
> How would this work? We then just expect LLMs to crawl it while leaving the
> live one alone?

Well, theres an incentive for LLMs and their human operator to crawl the static one,
as they succeed. with significantly less latency and less computational resources
thus less financial cost.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Old school: Use the lowest level language in which you can solve the problem
            conveniently.
New school: Use the highest level language in which the latest supercomputer
            can solve the problem without the user falling asleep waiting.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

      parent reply	other threads:[~2025-06-15 16:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-15 13:35 Michael Niedermayer
2025-06-15 13:42 ` Michael Niedermayer
2025-06-15 13:53   ` Derek Buitenhuis
2025-06-15 15:58     ` [FFmpeg-devel] Forensics Was: " Michael Niedermayer
2025-06-15 16:17       ` Derek Buitenhuis
2025-06-15 14:45   ` [FFmpeg-devel] " James Almer
2025-06-15 16:13     ` [FFmpeg-devel] Forensics Was: " Michael Niedermayer
2025-06-15 18:45   ` Michael Niedermayer
2025-06-15 14:53 ` [FFmpeg-devel] " James Almer
2025-06-15 15:57   ` Kacper Michajlow
2025-06-15 16:06     ` Marth64
2025-06-15 16:53       ` Michael Niedermayer
2025-06-15 17:03         ` Marth64
2025-06-15 16:48     ` Michael Niedermayer
2025-06-15 19:05     ` Michael Niedermayer
2025-06-15 16:28   ` Michael Niedermayer [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=20250615162831.GX29660@pb2 \
    --to=michael@niedermayer.cc \
    --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