FA’s Last Hurrah

We're finally learning the true side-effects of weight-loss drugs.

This is probably part of a front in the Fat Acceptance/Early Death backlash to GLP-1s. It was inevitable. That camp hates that these drugs exist. And this is why:

The vast majority of FA types are women and that someone can get so massively hotter in such a short time triggers their big (pun very much intended) intrasexual competition feelings. And that leads to real-world attempted actions.

Don’t let them get away with it.

Nothing To Do

This is true anywhere and always, but it has gotten worse. Most of the time when people argue with some point I’ve made I typically don’t engage because I realize they have not understood in the least and don’t even know what half the words mean.

Why get in the middle of that? Whatever is going on there has naught to do with me.

Enforce

I’ve observed this utterly bizarre constellation of beliefs in the wild before, too. Although calling any of it “beliefs” is really stretching the term far too thin as there is no cogent thought or value structure behind it.

People really can — and do! — believe that every country in the world has sovereign right to enforce immigration laws except the United States. And then act affronted or confused when you tell them that is it hypocritical to believe that.

The really strange thing about it all is they often completely cannot recognize that this is a contradictory set of opinions. Even if you point it out. Repeatedly. I have no idea what is going on cognitively there but is such an odd things to observe. And it’s fairly common in lefty types, perhaps even dominant.

CCC

Agreed with all of this. That Carney speech was cornpone catastrophic crapola. It’s spineless and it’s daft. “Embrace decline and failure” isn’t the brilliant rhetorical and managerial masterstroke the intelligentsia is portraying it as. I guess they must be this way, though. The alternative is actually doing something substantive: undertaking large projects; reversing decline; declaring the West worth fighting for.

And you know none of that is going to happen. So you get that milquetoast garbage from Carney and ilk.

Just a QQ

A phrase at work that instantly tells you things are about to get messy.

“Can I ask a quick question?” This is always, always a huge project. In IT, it’s never a “quick question.” Not once have I seen it be quick. Not a single damn time.

One of the “quick questions” I got in my current job turned into a project that is still rolling on eight months later. The person estimated it’d take five minutes. This is extremely common in my field.

In another role I got a “quick question” that transformed into a multi-year project and one firing. I think this happens because nearly all of the time managers and regular users have zero idea the complexity involved in anything, don’t do any research beforehand, and have no idea at all what they are asking for.

And then IT gets cursed with “quick question” poorly-scoped projects and tasks.

No Back

TIFU I messed up by trying to “repair” my girlfriend’s laptop.

What kind of clown does something like this with no backup?

Apparently, that kind of clown.

My first action on working on anyone’s machine for anything that has remotely any chance of changing anything at all is to create a backup. Even if they tell me it’s not needed. Even if they tell me not to bother. Even if they claim they just created a backup.

That has saved my ass so many times.

NAT Not

IPv6 is not insecure because it lacks a NAT.

Not this asinine shit again. I hate this idiot and idiots like this in general. That is, the “Well, ackshually” shitheels who ignore how anything is in the real world, standard practices, and how things actually work. And also do not really understand the tech, either.

First of all, you stupid motherfucker, a device can (and most consumer crap does) implement NAPT/PAT with dynamic state but often has1 no explicit packet-filter policy engine (what most people would term a “firewall”), yet will still refuse unsolicited inbound flows simply because these flows donโ€™t match any mapping/state. That is in fact de facto protection via reachability restriction. And that behavior is explicitly defined in NAT RFCs. The NAT RFCs in fact directly discuss filtering behavior associated with NAT operations (not just a separate firewall). Check out RFC 4787 (BCP 127), RFC 5382 (BCP 142), RFC 5508 (BCP 148) and RFC 7857 for how NAT really works. I’ve read those documents in toto several times over the years. I can guarantee that doofus has not.

Miraculously, he is right that โ€œNAT isnโ€™t designed as security,โ€ but the clown-ass shitstain then uses that to imply โ€œNAT adds no security value,โ€ which is false in actual practice. Nearly every existing IPv4 NAT (NAPT/PAT) gateway2 enforces stateful inbound blocking out of the box. This NAT — independent of the router’s firewall function — does provide decent default-on security for home users.

On the other hand, his core premise (โ€œmodern routers default-deny inbound IPv6 anywayโ€) is absolutely not a sure thing. Standards and real deployments often have non-optimal defaults, including configs that default-forward unsolicited inbound IPv6 traffic. This is because unlike IPv4, IPv6 expects end-to-end connectivity. So that means many router vendors ship equipment that way. Thus, having NAT adds quite hardy extra protection in practice. That is to say, with any IPv4 home NAT you need both a firewall hole and a port-forward/mapping mistake to expose a device. With IPv6 global addressing, exposure can occur with only one minor screw-up. Then boom, your whole network is out there on the wide-open internet.

This disphit’s NAT explanation is also crazy sloppy (he frames it as mainly destination-rewrite based on static port forwards), just glossing over or ignoring that the real โ€œdefault denyโ€ effect largely comes from dynamically created state. He overstates a conditional truth (โ€œIPv6 is fine if you keep equivalent edge filteringโ€) into an unsupported and often-wrong universal claim, using cherry-picked vendor defaults as if they were always the case. Also, he deliberately handwaves away as irrelevant the safety margin NAT provides in reality every damn day.

NAT wasn’t designed for security, wah wah. Carbon steel wasn’t designed for armor, either, but we use it for that in the real world.

My conclusion: Fuck this fucking clown who doesn’t know a damn thing, and what he thinks he knows is wrong. Read the RFCs, motherfucker. I’ll wait. You won’t understand them anyway, but I’ll still wait.

  1. And does not require.
  2. I have not seen one in 20+ years that does not.