I don’t get why twitter wouldn’t just comply & implement measures the moment it knew it’s platform was being used to distribute CSAM.
I don’t get why twitter wouldn’t just comply & implement measures the moment it knew it’s platform was being used to distribute CSAM.
“I felt a great disturbance in the Force, as if millions of voices suddenly cried out in terror and were suddenly silenced.”
Same stance the UK Post Office took with Horizon. A fucking stupid stance…
The key differences is utilities you’re paying for the generation & maintenance of key resources - without gas, water and electricity we wouldn’t be able to survive. Road tax you’re helping to pay for the renewal and upkeep of the road surface (among other local services)… Left alone the road will degrade & will become unusable.
Suspension as a Service is milking what should be a perpetual cost when purchasing the vehicle. If the hardware is already installed, it should be available for the owner to use. They’re not paying for the upkeep of the vehicle, or even ensuring the suspension remains functional… All they’ve done is placed the function behind a pay wall. They can argue they’re maintaining the software, but it’s utter bullshit and I hate the fact this has become a norm within B2B (for example network appliances)
At least with luxury subscriptions such as Spotify, Netflix, NYT, etc you’re getting access to their content, which they renew. Here you get access to something you should have had access to from day 1.
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.
Why? Its hardware is dog shit.
IPv4 isn’t depreciated, it’s exhausted. It’s still a key cornerstone of our current internet today.
We still have “modern” hardware being deployed with piss-poor IPv6 support (if any at all). Until that gets fixed, adoption rates will continue to be low. Adding warnings will only result in annoying people, not driving for improvement.
Surprised she didn’t freak out with the line below. It’s already gone on a killing spree…
Technically it’s always hitting the road & air, so it simple just doesn’t move.
Podman ftw!
Much like naming a company “X”
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.
IPv6 has NPTv6, which allows you to translate from one prefix into another.
Useful if you’ve got dual WAN, and can’t advertise your own addressing via the ISP. You can use NPTv6 to translate between your local prefix and the public prefixes. But NPTv6 is completely stateless. It’s literally a 1:1 mapping between the prefixes.
I don’t know, but my electric bill is certainly painful.
Explains why insects are always trying enter - must feel like a mansion!