superkuh

Anubis is the only anti-"rude corporate http requests amounts" that doesn't only rely on cutting edge javascript VM features. Simple mitigations like the HTML header meta-refresh proof-of-work(waiting) work in all browsers going back 20 years. Rather than just supporting browsers from the last 3~ months like cloudflare.

Subheadline: site owners unaware or don't care about humans caught in their "effective" block

Would dropping these specialized ipv4 syn packets with extra header size beyond 20 bytes (as indicated by options value >5) with the firewall be low enough in the order of things to mitigate the attack? Like, iptables -A INPUT -p tcp --syn -m u32 --u32 "0>>24&0xF=6:15" -j DROP ?

This is where the very simple and stable "server side includes" (SSI) that every major webserver has had for 30 years come in. It's just enough templating power to make menu.html and include it in every page you care about without any significant attack surface. Working with static HTML fragments on the filesystem is such a delight compared to any CMS.

You know what would be really ambitious? Software that exists in a stable form without breaking for more than 15 years. Truly ambitious would be a stable, non-changing common linux base (like how Nintendo NES emulation target is stable) of packages that just gets supported for decades.

Perhaps that's too ambitious. But it would be of incredible utility not having to re-make the same things over and over in pepertuity with ever more abstraction layers. So much work on computer is just the constant churn and future shock of libraries adding new features which require updates which break other things. I'm tired of building castles on sand.

Uh, no. This headline is wrong. It's FP32 unlocked from being halved, not 16 bit ops. And to be clear, over the last week I've looked many places and I've not seen any reports of this unlock being applied to any 3xxx card except the 3090/3090ti series. Even if it might apply more generally in theory.

You say, "Play Protect" as if it is a thing that users can choose to avoid. Or as if it justifies the behavior. I don't think either of those is true.

There's a reason that high speed switching electronics have metal cases. And it's understandable that most people don't know babinet's principle as it applies to RF antenna (basically a hole in a conductor is exactly equivalent to a conductor of that same size and shape: the case window is an antenna). The FCC wouldn't care about me because I intentionally use full metal cases for all my high speed switching electronics and monitor my RF environment from 20 to 3700 MHz over various SDR devices 24/7/365.

I'll grant that a ~meter size slot antenna (case window) is not exactly big enough to be resonant at HF but compromise antennas are the standard for HF and they still work; just because HF propagates so well even at low powers. And lets not forget they such a case window slot antenna is resonant around higher frequencies like ~144 Mhz where the GPU memory is blasting and pulling large currents over long conductors.

If the FCC actually tested a modern computers in their shipped window or completely glass computer cases they likely they wouldn't allow it to be sold commercially. But they're much too busy with politics and as long as it doesn't interfere with military use or high frequency trading they don't care about HF.

Anyway, I do see that no one is disagreeing about the radio intereference caused by plasma TVs. That's good, because they're terrible offenders.

Understandable stance, re: comments, but this even applies to the descriptions of your own videos. And actually, in comments, I can still sometimes post URLs. So it's not even consistent or applied where it would really help.

Plasma screens, like computer case windows, are incredibly rude but the people using them have no idea that their behavior is inappropriate. Both emit significant amounts of HF radio interference which bounces around the ionosphere degrading a shared resource for all of Earth. And even more VHF and up interference which only degrades a shared resource till the next hill. It's pretty much just like littering in a public park.

On Google's Youtube to post links (like in video descriptions, etc) you have to pay by adding sellable/monetarily valuable personally identifying information to your account like a phone number and ID. Otherwise even with a google account from 2006 in good standing you can't post links anymore. Attempts to edit old video descriptions with HTTP/S links (from before the policy) also don't work.

Almost as crazy as running random arbitrary code from unknown third parties automatically. Yet that's the unquestioned status quo for the web and if you don't do it you're considered a weirdo. This is whataboutism, of course, and does not invalidate your claims. But really the only risk comes from the harness that does tool calling, not inference. Just running inference without it is not at all risky.

It's too late. Drupal 6 turned me off ever using a CMS again. Now I purely use html files in folders with other files in folders. It's great. No maintainence burden, no attack surface, no resource eating always running programs or database that can get corrupted or otherwise in a bad state. And especially no migrating to the new version and everything breaking (especially with non-core stuff).

Nothing about abliteration matters here. Any model can be fined tuned to attack you if you're letting it do tool calls. But I trust a random human enthusiast and community feedback more than I trust a megacorporations that commit crimes without any prosecution or consequences.

What we really need form Lets Encrypt is stability and lack of change. But LE is just following the megacorps down the current TLS road. We're already down to only 30 day certs and on the second iteration of acme. Acme original protocol setups no longer work, they were broken by the dropping of support.

Addding new methods of validation does not help nearly so much as just supporting existing methods for more than a few years would. The race to the bottom will end up with an incredibly fragile system that breaks the moment automation does. Combine this with the trend towards HTTP-only and any given website will only have a lifetime of a couple years without direct human intervention. This is a drastic change from the status quo of websites simply lasting forever and being accessible till their webservers stop.

It is 100% a corporate-for-profit-only mindset and architecture. LE is not designing or accomidating human person goals and needs.