Well, the strains that I listed are in the Sanofi Quadrivalent vaccine that is most popular in Europe (and being administered right now) as far as I know...
2,490 karma · joined December 13, 2022
In Europe, for 2024/2025, types A 'Victoria' and 'Thailand' (with type-B 'Victoria' and 'Yamagata' following closely, so you can see it's still there-ish) are expected to be the most virulent. but, as always with influenza, this might be wrong, which means vaccination might be slightly less effective, although still beneficial.
If all you need is simple compute and bandwidth, and you can spare the resources to admin a server, of course you'll be able to find colocated, dedicated-server or even VPS solutions that fit your requirements and are way cheaper than AWS/Azure/GCS/etc.
The whole selling point of 'cloud' is that you can scale infinitely at a moment's notice and have a whole array of batteries-included services at your disposal. Don't need that? Don't do it, even if it's fashionable...
But, as with most situations, "let's put up a sign" somehow didn't resolve the issue...
This feels more like a situation where the baboons realized that "these humans have yummy stuff" followed by "hey, and this is how we can distract them in order to grab it"
But, well, semantics...
This a relatively large lot (being at the round-turn point of a one-way route), with both personal vehicles and tour busses coming and going. There are also a lot of baboons. On the narrow-ish mountain road up and down, these already pester the vehicles every way they can, but once parked, it's when things get truly special, especially for the tour busses.
First, the baboon females parade past a bus, with infants on their back. The tourists are delighted by this, and rush out with their cameras. Then, the females retreat into the bushes, which further distracts the humans.
Then, the males, which have been hiding in the nearby trees, descend upon the bus, and absolutely ransack it. Everything that can be taken (and that's mostly bags and coats) gets dragged into the trees. Then, they triumphantly go through the loot, redistribute anything that's edible or otherwise interesting, and toss the rest.
It's scary how well these animals instinctively understand the way we behave...
I truly don't know, by the way; this was merely an example to illustrate my perceived difference-in-complexity between Linux and OpenBSD, which might be entirely misguided, but definitely part of the issue the article linked in the submission hints at?
In fact, OpenBSD has gotten a lot more verbose over the years, due to sub-processes being listed explicitly. Good example here is `smtpd`, but even then, the difference with Linux remains... stark.
On OpenBSD, the list of processes is mercifully short, and I can tell you what each of them is supposed to do. CoreOS? Not so much -- and, yeah, I know, I could of course switch to non-systemd-infested distro, but even there, there would be at least a screen-full of processes of which I could maybe identify half?
This pattern extends to configuration: OpenBSD has a handful of very-well-documented files in /etc, whereas under Linux, things are literally all over the place, and you might even end up editing irrelevant configs, because they happen to be regenerated by yet-another-layer of tooling, or your distro is simply not using the tool you think you're configuring...
Still, I have no clear preference for one OS over the other! With workloads being mostly containerized these days, it's so easy to roll out a new VM, that the level of understanding required to, say, nurse a broken OS on physical hardware back to health, is now simply irrelevant. Just blow away the old and deploy the new, and forget about it.
On OpenBSD, the deployment tooling uses tried-and-true commands like `fdisk` and `ifconfig`, whereas for CoreOS it's YAML (pronounced: 'hell'), but the truth is... it doesn't matter that much. Getting the base OS installed, adding some volumes, creating sub-interfaces for the relevant VLANs, installing Docker(-compose), and getting the containers to (re)start is all very, very similar.
So, yeah, I sort-of get what the article is trying to say, but the ground-truth I think is that in most cases the OS isn't that much of a differentiator anymore, as they're pretty much all OK-ish...
So, the issue becomes "how to fix this"? This very same site tells me that EU-style hardcore regulation "makes it impossible to run a business", so, I'm open to suggestions, other than "Open Source Everything and Rewrite it in Rust"?
The first 3 parts aren't that complicated (literally a few sectors with fixed content, maybe a few pointer fixups), and no reason IMHO to want to kill off ISO. Generating that actual file system is the hard work, but also required for live-USB distros, which circles back to the point being made in the article eluding me...
And, no, UDF isn't great either, but I wouldn't say it "has to die": it's a pretty convenient distribution format due to being widely supported, as it's really simple to implement.
So, this mostly seems to be a rant against live-CD-style Linux distros, since those are hard on maintainers (plus: toxic community multiplier)? On the one hand that might be true, on the other hand, the 'hey, here is how you get an ext4 or whatever filesystem in RAM' tooling around that is so mature and convenient that it's hard to see why, and I can't distill any real arguments from this...
Not sure about the business model or anything else, but from a technical point of view, this sort-of made me smile.
Glancing at https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/BIOS/... seems to support this...
No, that's the exact reason why OS/2 checks the OEM ID. The volume label was initially used to detect disk swaps (so that if an application has open files on disk 1, it does not destroy data on disk 2 by writes after the user replaces the floppy in the drive, which could not be detected in hardware until much later, and even then not unless you were using a Mac, basically).
Of course, the volume label is user-set (so duplicates are possible), and more often not set than meaningful in any case. So, DOS 3.3 added the (unique-at-format-time) volume serial number. Which was always all-zeroes (or garbage) on pre-3.3 disks, hence the need for the OEM ID check.
And the devastating effectiveness has just been live-demonstrated to an audience very interested in that kind of stuff.
So, yeah, air travel is going to become, eh, a bit different, soon. Get those cellphones and laptops with removable batteries while they're still available (and ensure the packs are models you can easily buy at your destination), as anything battery-powered is going to be off-limits in both the cabin and the cargo hold as soon as the now-extremely-motivated international terrorist community gets around to downing the first, oh, three airliners or so?
Possibly, Chrome/Edge support the same or similiar mechanisms, but I haven't checked recently.
Alternatively, your school uses a HTTPS middlebox that knows how to distinguish DoH requests from regular SSL traffic to 1.1.1.1.
In any case, this is most likely not an 'attack' on you, and characterizing it as such is unlikely to lead to fruitful discussions around the policy.
Going public in the US was absolutely not the correct choice for them. Other than, quite obviously, not being able to keep up with the accounting requirements (which are, like, 80% of the job for any public company, the other 20% being split 80/20 between 'keeping shareholders happy' and 'doing the right thing'), they just lost sight of their core market, which used to be "cutting edge reference design boards for people who know what they're doing."
Instead, we got "packaged solutions" that included overpriced RAM and SSDs/HDDs. Well, sure, if I'd wanted that, I'd rather go to Dell/EMC! Because they at least have the delivery capabilities, which Supermicro has also been under-performing on for the past years.
So, yeah...
For SMTP: log optimization.
Like: yeah, I don't care that you're self-DDOSing if you're an actual spammer. But, just in case you're a legitimate sender lacking SPF records, and you just need some help, I still want some kind of signal.
For SSH, I guess you might want something similar, just to catch authorized-yet-misconfigured remotes...
My own experience with this is not as much with SSH as with SMTP. If your particular IP emits a single non-deliverable message every 30 minutes or so, that's fine.
But: more than a handful of SPF failures for the same sender/recipient combo within 10 minutes or so? Yeah, you're now on the general-deny-list. And persisting even then? Automagically tar-pitted on the firewall, and have fun...
I've never had iOS (either the Cisco or the Apple variant) randomly apply CamelCaps, though. One more thing to look out for in the future :)
I've spent, like, several minutes of my life trying to figure this out, and... came up blank?
The title is not copied from the PDF, where such issues would be rare but not unimaginable. I also couldn't find any articles linking to this PDF with this particular title.
So... a misfiring accessibility solution? Solar rays directly going for the Shift key?
(P.S. Yeah, I know "Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting." -- but this seems sort-of uncommon?)
Anyway, I don't find these questions intrusive as much as 'not fit for purpose', with a bit of (cultural) insensitivity mixed in. I once had to console a very-upset very-serious person from an African country with regards to the the 'name of pet' question they just had to answer as part of a mandatory signup for a US-based third-party service, and which they just couldn't find an answer to.
And whenever I'm asked about "name of high school" or (even worse) "high school mascot", I'm tempted to flip out with something like "yeah, which of the seven-or-so I attended, for no-fun-at-all reasons, and most of which I don't even remember, but I can assure you none of them had a mascot", but then I just take a chill pill and mash my keyboard...
I won't, but you be you...
The days-long airport chaos that most of the world just went through recently would suggest otherwise?
Good to hear that things changed, though: for me, it's a bit late, but, hey, I'm not your target audience anyway.