I think the assumption hosting providers are "reasonable" (which is what both you and Cloudflare assume when arguing against DNS providers should not be responsible for filtering their results) and can be pursued legally sadly no longer is true (and that is putting aside IP laws), so courts naturally move up the chain. I can't see with the current state of the world that a splinternet isn't already a reality (e.g. the Great Firewall of China), given contradictory regularity environments.
Quad9 isn't even a hosting provider, it's a cache. Caches are explicitly not liable under the EU DSA. But a court can still order anyone to do anything that's reasonable, including ordering a cache to implement blocking.
I wonder if Quad9 failed to argue they don't have the technical capability to do blocking. I think that's the most effective form of pushback against an arbitrary court order. As a programmer we think "yeah I guess I could program that, so I tell the judge I have the capability" but the more robust legal perspective is "I didn't already program that, so I tell the judge I don't have the capability, will you order us to develop the capability?" Being ordered to develop a capability is going to be a higher legal bar than being ordered to use one you have.
Apparently Quad9 has the capability because they have an ad-blocking DNS service. This should be a lesson to the rest of us: if you have a blocking capability, you will be compelled to use it.
Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.
Comments should get more thoughtful and substantive, not less, as a topic gets more divisive.
When disagreeing, reply to the argument instead of calling names.
Where? See the start of the submitted (which does not mention youtube, but if you follow the news it is there):
> In July, France joined Australia in restricting minors from accessing social media—barring children under 15 from major platforms, before the ban was blocked by the country’s top court on human rights grounds. The UK aims to forbid kids under 16 from accessing Facebook, TikTok, and other platforms in early 2027, and the EU has announced its own plan to prohibit social media for kids under 15
Explain the difference. Because if something declared "Age verification for entrance into cultural venues", my first matter of care is not about the point in the future where the liability would happen - the core liability is already there, proposing the satanic.
The proposal has already happened. You are not understanding what you reply to.
> the core liability is already there, proposing the satanic
We cannot be in a situation in which ___trash___ is making proposals (threats) and our reassurance should be "maybe they will not". The reassurance happens when they are called with their deserved name by a critical mass.
No, it's already legislation in some countries, and advanced preliminary work in others, and declared determination in others again. As more people have noted, you are not checking the contents in this very page.
And your insistence on "not there yet" is again completely bypassing our arguments about the severity of the context.
Nope, the whole point of this is to remove the coupling for UTC. You can either have monotonic time (or at least per-observer monotonic time), or you can follow earth's rotation. Choosing monotonic time is perfectly fine (and feel free to pick your epoch and time unit), but like we have timezones such that 12:00 means something (mostly), having the human conception of what time means does imply that we do kinda need to look at what's happening outside.
It's fine for them to exist, and probably better -- you can land incomplete things behind a feature flag and avoid some amount of rebase/merge hell.
But they should be marked experimental in that case, not optional. Optional flags ought to work together, or at least it should be considered a bug worth quickly fixing if they don't. Combining experimental flags otoh is Buyer Beware.
I'm not sure what you think specifically needs maintaining, it's the same as LAMP, LEAN, JAM and the various stack acronyms? The BSD you choose is naturally maintained by the various BSD distros (though there's an implicit assumption of OpenBSD as will become obvious), C is C (so defer to your C-complier), httpd comes from OpenBSD (https://man.openbsd.org/httpd.8), and SQLite is SQLite. You can naturally choose to add additional libraries (some are suggested on the site, I don't know what their status is, but the article includes libcurl and libsodium, which are also well maintained), but as the example shows, you don't need much to start with. A key thing that's a bit hidden is the use of CGI and the various OpenBSD hardening tools (e.g. pledge, unveil), which make exploiting the C binary much harder than on other systems.
Given https://www.abc.net.au/news/2026-10-10/how-firmus-the-bigges... and the above, I'd say we're already primed for a fall. Given 5 years is a pretty long time (that's 3 US elections cycles where politics can increase uncertainty about AI), and the length it took for the subprime market to create the GFC (see e.g. https://en.wikipedia.org/wiki/File:Subprime_mortgage_origina...) looks to be about 3-5 years, I'd be 99% sure the crash would happen by then (with the 1% covering both the uncertainty in the cycle and something odd happening).
reply