MarkovChain242

Tip for savvy EU-based employers: you can save yourselves a lot of work when hiring US nationals that don't quite meet the European Work Visa requirements, by requesting a humanitarian visa for candidates that live in Florida and such instead. Abortion restrictions and associated death penalty pretty much make that a no-brainer.

Yes, could, assuming that the AP supports it -- and nobody seems to be in a big hurry to implement that. After all, 802.11h has been standardized since, like, 2018 or so, with exactly zero mass-market support so far.

Absent a proper 'how to join the local Wi-Fi network' story, IoT connectivity is converging around LoRaWAN anyway.

As I said, I like the 5GHz support, but spinning it as 'power efficient' is a reach.

5GHz support on an ESP32 is something everyone has been waiting for for a loooong time. So, that would be good I guess?

But in general, 802.11ax is orthogonal to 'non-stop battery-based connectivity', so we'll have to wait and see how well that works out.

(Assuming they ship this one, and assuming anyone will be able to buy one in the next 2 years or so.)

This is sort-of cool, I guess, but also very much not what you would want to do?

I mean, people agitate against `curl blah.xyz | sh` for a reason.

And this, by any measure, is much worse. Also: 'By default iPXE does not compile in HTTPS support'

Yeah, I would love to be able to buy an ARM server (or a RISC-V server), but so far that's just impossible.

Let's just limit the discussion to Ampere. There is supposed to be Gigabyte G242, with several SKUs, that supports an older version of their chips. I've had extensive email discussions with Gigabyte sales staff, and yet I've been unable to find a single reseller that will even backorder any version of the G242 for me. And there's even a G252 now. Lovely!

Yes, there is a supply chain crisis. Yes, ordering novel products is never easy, nor cheap. But, heck, do I understand why Intel has a lock on the server market...

Agree that analyzing DNS requests is the highest-value infosec practice when it comes to detecting compromises in enterprise networks.

Shame that (mostly US-based) ISPs realized the same thing (albeit for entirely different purposes), and therefore DoH is now pretty much the default.

And ensuring all DoH requests go through a corporate proxy is... not entirely trivial. On Windows, all major browsers respect their respective group policies, but that doesn't help for mobiles and such.

Shame!

I like

"just shadowban the oaf"

As currently practiced by all those who fear the populace-driven wrath of the auto-Dang...

My personal favorite story in this genre is that the set-top box that my employer-at-the-time imported into the US called the schedule "TV Guide."

PM: "TV Guide" is a Registered Trademark. You can't call it that! Non-US-folks: "Uhm, TV guide is just, ehhm, what it says" PM: "We'll be sued! We'll be wiped out" Non-US-folks: "Uhm, OK, so what about 'TV Listings'" PM: "Oh, yeah, that will be OK"

How any of this makes any difference still eludes me, but yeah...