Hi Torbjorn,
On Tue, Aug 18, 2026 at 07:06:08AM +0200, Torbjorn SVENSSON wrote:
> On 2026-08-17 09:58, Jonathan Wakely via Gcc wrote:
> >On Sun, 16 Aug 2026, 23:12 Mark Wielaard, <[email protected]> wrote:
> >We should add
> >>authentication through patchwork and wiki. And add some way to
> >>manually authenticate an ip address. If nothing works please email
> >>admin-requests@ to get yours added.
> >
> >I forgot to say that the problems I was having were on my mobile phone,
> >because I was in holiday until yesterday. I don't have a fixed IP on my
> >phone (especially not when using data roaming abroad). I couldn't ssh to
> >the server, because I was just trying to browse web pages on my phone (and
> >didn't have any ssh keys with me on holiday).
> >
> >Now that I'm back home it works fine from my usual static IP.
>
> I have sort of the same issue.
> On my computer at work, we are using a proxy solution that prevents me from
> knowing what endpoint IP that is going to be used. As a result, I think
> I end up coming for different IPs for most of my accesses and either hit
> the Anubis check and/or the 429 error.
If you know your outgoing ip/nat net/range (and your company doesn't
run its own scrapers), then please do feel free to sent it to
admin-requests@ and we can add it as an manual override.
> After a few refreshes, I usually get access, but it gets really frustrating
> when you try to post comments on bugzilla etc. Keep in mind that this when
> I am logged in!
anubis has a special "bot-dont-POST" rule that makes sure you don't
get interrupted by an Anubis challenge. Maybe the limiter needs the
same and just let POSTs through and only limit GETs?
> As the 429 error is suppose to lower the amount of traffic to the services,
> it's somewhat counterproductive when users will have to send, not 1
> request, but maybe 10-20 to get the resource they seek. Maybe this is
> still a gain overall, but, to me, it feels like we are heading on the
> wrong path if we want to help our users.
Yeah... note that scrapers come and go in waves. You might just have
hit a bad wave (last week/weekend we saw 2k+ hits/sec - all from
different IPs, today it is "just" 150 hits/sec). So hopefully your
experience today is smoother.
Our first priority is making this as good as possible for our project
developers and contributors. So find some way for them to get
authenticated and then get them around our limiters. For the general
public things are indeed not on a great path :{ I am afraid we have to
wait for the AI bubble to burst and/or to get these residential proxy
companies declared illegal.
Cheers,
Mark
