This BS needs to stop, it is very anoying!

You are aware that the owner of this site works for DataDog, right?

1 members found this post helpful.

Jeremy works for DataDog? No, I wasn't aware of that.

Hey, I have a workaround to the LQ delay problem.

I'm on protonvpn, with the CLI scripts because their 'official' driver requires systemd. So I can change my IP easily. I have an alias set up to allow disconnection, and another allowing connection that takes one country code argument. If you change ip, stop the page that's not coming in & reload it - Voilà! It's there. No delays.

EDIT: Ergo, that proves cloudfare is causing it!

That is not LQ, that is Clownfaire itself. Personally I would avoid using the service and do the caching myself on my server, but that may not be an option for LQ. (I mean, unless we all want to start paying for access... And many of us CAN'T!)

If it helps, the open issue here is at https://www.linuxquestions.org/quest...d=273#note1059

I have always been able to get by without trusting cloudflare in noscript. Things changed yesterday.

So on Friday I didn't need to trust cloudflare now I do. What changed?

I hope you are not waiting for Clownfaire to tell us. They rarely admit to errors, and when they do you never get the entire story. (They are not as terrible as some, but nowhere near transparent either! )

I get the cloudflare screen and fairly quickly, an "authorisation". Does this mean it's doing a quick search of my system? I hope not!
What I've also noticed since the appearance of cloudflare, is that everything on the lq site takes much longer to load.

Confirming that there is an ongoing network attack aimed at the site. FWIW, without Cloudflare the site would have been 100% unavailable for the entire duration, vs slow or sometimes not available. We're continuing to investigate.

--jeremy

9 members found this post helpful.

Thank you, Jeremy. I wish we had been told this when the problem first blew up two days ago; it would have made everyone a lot more patient.

2 members found this post helpful.

An ongoing attack, eh?

I wonder are they slow upstairs, or have they noticed it's not exactly working?

It is working, at least from my end. Friday & Saturday the site was mostly unreachable, and when it was reachable, it was too unresponsive to use. Now, I hate Cuckflare with words that are unprintable here, but, because of the way the modern internet is, it's them or nothing. They are one of the four gatekeepers of the internet - the others being Spamhaus, Apple, and Google. These four, often based on politics, determine who can access what and if. But that is a topic for another place. At least I know what's going on now. I figured it seemed a bit ddos-y as of late.

I knew it. Fortunately, Cloudflare's "mitigation" is much less annoying today.

If a counterattack is legal and justified, I am willing to help.