From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 51B654F0A9 for ; Sun, 15 Jun 2025 15:57:27 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 3AA9868D2FE; Sun, 15 Jun 2025 18:57:24 +0300 (EEST) Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 8FAB868CE3F for ; Sun, 15 Jun 2025 18:57:22 +0300 (EEST) Received: by mail-ed1-f49.google.com with SMTP id 4fb4d7f45d1cf-606ddbda275so7293534a12.1 for ; Sun, 15 Jun 2025 08:57:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750003041; x=1750607841; darn=ffmpeg.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=MDahD9oa0Ftv1AwrJGzXZFIzt5RLnzFfxdiwunviYM8=; b=K5EyvPX/RVcNCFjF9o2wqcU6qye0PkuZmicDzm+lKUe7zc9BnD+FDCH/ek6lvEXY7P 43LK8SxvjZ3VfNnRRlf9p1XWNhhBOaP+/Y0UgfflTHvAgbrVPZLHyOsfDB9YYBaD2gYA 5WhwvPpSPy8lvDYbiH39lBNzGaV8vxmj6tgfH4qmKAfC6fO6QccDSiV8ysQemONtfxz8 rjdO0eMZ+8KiH5pLQnN35V49OJVsP39JujurKwiu3nySoA7mg71XlXgn69nd263b3luc 19se80IT3RW2arOFJaKn5up2VEVGCmLQVnWJfp1UxPqs7BBlczf7wxYQCkC68PB0/DL+ nXgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750003041; x=1750607841; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MDahD9oa0Ftv1AwrJGzXZFIzt5RLnzFfxdiwunviYM8=; b=oPRV5I5sOTzG8w8tvlJP8DD87WoVyAxEv2pAkmVdu9sZe3IZo8xMIEACy3GhP+Ervb ft6OpJqJ8iwB2nTqoj2T7g6/ONaM0nrJUdovtth51V2jzcd+HABWsr2/oKniAW1cqIpG Si9gkf1tddav8NdK9Ozq3o7ojgk8S9MTG5ZoHzJRQYx5VnVi0LW1svpLOo861IIgPnCi NhcCsmtYD+K6QlByDTwW+Km/ICliqtA6s4ynPAoaNTj0z2YCVGc+ykrfhJhWP0PQKYyH UKrBq0eFCG8BzrYfS8OsGTwJHt5UXApYBReMU3BlHhTDqcmGeki6rz5oP3YhsYmRPwNc 3hWA== X-Gm-Message-State: AOJu0YwrVZAchxvma5krtTSjL9npXKIbC+8FW06SBpi1TsfUPfAaIrtS dAbYsyEiJNsFRyZFhUtGvwLMA50wkNim6xR0dudL/0ONnzfuWvw5OLWH/+sltRqh4p/+OqPQ+7U 3K5JXanGWUQ7kKlqZIW2oxSRaOhkcso+npdN7 X-Gm-Gg: ASbGncuRPSZdu7kw0QSi/6NqrQs5kb0+MEceIpnSOWsP1w+r36zVoq47Y0nPG8Ly/Dc 0OXUetE19duMT6BOsKpzMIPrkmpg3ScCCfHKTw4pu3AzwolReOF8m8qN9GHx1I3IGPMjvkvKrdf KHhOy6xPTLixLX+ctLq6NL2sOLgVjQRZZyknZNe6Aw X-Google-Smtp-Source: AGHT+IGAxGQ4qFUb2anTwkTE8dLWzllBQ7pIRPFHGCHwZ902dSRWdwzNwXqpUxYcqgUjfuT3aTs0Wv3HxZifzW5q9pI= X-Received: by 2002:a05:6402:358c:b0:607:f431:33f5 with SMTP id 4fb4d7f45d1cf-608d097abaamr6148515a12.25.1750003040615; Sun, 15 Jun 2025 08:57:20 -0700 (PDT) MIME-Version: 1.0 References: <20250615133515.GT29660@pb2> <981c3a86-57de-4626-90a8-b236a6987216@gmail.com> In-Reply-To: <981c3a86-57de-4626-90a8-b236a6987216@gmail.com> From: Kacper Michajlow Date: Sun, 15 Jun 2025 17:57:09 +0200 X-Gm-Features: AX0GCFtnhlWPlkodIJY4AdX_zj0T3oV562-TBc8M9qaHJOlpaWJCK__kP37WrB0 Message-ID: To: FFmpeg development discussions and patches Subject: Re: [FFmpeg-devel] [RFC] statictrac, trac and caching X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Sun, 15 Jun 2025 at 16:53, 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? > > Maybe requiring to be logged in to actually access the bug list would > workaround this, leaving only the wiki open. Or requiring to be logged > in to access attachments (Which afaik was what most bots tried to fetch > yesterday). Allowing public access to the bug lists is important for visibility and for search engines to index the bugs/discussions. Ideally we want users to find the first party trac first, instead of some dodgy forum when searching for bugs/solutions. Maybe it's time to retire the trac? It is quite slow by design and not really actively maintained anymore. Holding onto legacy software always increases the burden of maintainability. But as mentioned on IRC, it seems to be classic DDoS, so likely not something that would be easily circumvented by any access restriction. > These look like residential IPs from a botnet (all same ISP, so possibly compromised > IoT device). > > Publishing these seems in poor taste. This. - Kacper _______________________________________________ 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".