

It wouldn’t stop against volumetric attacks…
They’d still fully consume the WAN bearer regardless of Crowdsec protecting the endpoint. For that you need a scrubbing centre to dump the traffic onto.
It wouldn’t stop against volumetric attacks…
They’d still fully consume the WAN bearer regardless of Crowdsec protecting the endpoint. For that you need a scrubbing centre to dump the traffic onto.
Now I’m wondering what the minimum amount of water required to sustain the current levels of life on earth.
Podman ftw!
Sounds like the DNS TTL (Time to Live) is set extremely low, preventing clients caching the record. Each time your browser makes a request (such as updating the graphs), it’s submitting a new DNS query each time.
According to this post, this is intentional behaviour for PiHole to support situations where you change a domain from the block to allowed. The same post also references the necessary file modifications, should you wish to extend the TTL regardless.
The only downside you’ll notice is a delay after whitlisting a domain, and it actually being unblocked. You’ll need to wait for the TTL to expire. Setting it to something like 15 minutes would be a reasonable compromise.
Zero sympathy. If they wanted to reduce the amount of illegal streamers, all they’ve got to do is make their content more accessible.
Release it on multiple streaming platforms, not just their own. Ensure its released globally at the same time. And get rid of the geo-blocking.
The lack of reasonable legal alternatives is what drives piracy.
I have questions…
What was Meta’s defense for a social media site to need sensitive sexual and reproductive health data?
And if Flo was UK based, surely that data should have been covered by GDPR. How was Meta a partner with legitimate interest to PII data?