fukawi2

PICK D3 has been doing similar since... well, a very long time. It uses chr(254), chr(253) and chr(252) for the varying depths of records. I always rather enjoyed working with it in the 2000s. Elegant in its simplicity, functionally practical (for the workloads we had at the time at least)

Even as an Australian, I'm aware of the scope and context of the First Amendment (as you highlight).

How are so many Americans so mistaken about their own constitution?

That's not how TTL works. Or do you mean propagation after changing an existing RR?

It's "common" to lower a TTL in preparation for a change to an existing RR, but you need to make sure you lower it at least as long as the current TTL prior to the change. Keeping the TTL low after the change isn't beneficial unless you're planning for the possibility of reverting the change.

A low TTL on a new record will not speed propagation. Resolvers either have the new record cached or they don't. If it's cached, the TTL doesn't matter because it already has the record (propogated). If it doesn't have it cached, then it doesn't know the TTL so doesn't matter if it's 1 second or 1 month.

This is what the NETMAP target in iptables is for - map an entire subnet to another subnet, including the reverse. We were doing this 20 years ago for clients trying to on-board other companies that they'd bought. It's horrible, but it does solve the problem in a pinch.

I do not understand this rhetoric of Apple hardware being so amazing. The only moderately impressive thing they've done for years is the M chips. Beyond that, it's just crippled, overpriced, and unrepairable.

They have shiny cases, yay. I'll take my ugly Thinkpad and actually get shit done over a shiny case and glossy screen.

Finally, a comment that understands the concepts instead of insolently ranting about how useless it is.

Social media ban for under 16s is the latest half witted idea enacted by the government here.

We just got a whole bunch of new radios for fire brigade in our state. Every radio has a SIM and fails over to the public cell network if the primary (licensed) network is unavailable.

Which ironically is one of the first networks to fail when we have widespread storms etc.

Visual distraction in IDEs is amazing. I see my co-workers using Visual Studio or something, and I can't even identify the code they're working on among the mess of the screen. There's so much going on. The clean and pure display in vim in my terminal let's me just focus and get shit done. I honestly don't understand how they get anything done, but to each their own.

While you're technically correct, what I gathered from their experience is the consistency of usage, between not only their own projects but third-party projects too.

They could make technical improvements to their own Makefiles, sure. But it's more about being able to enter a project and have a consistent experience in "getting started".

Which is ironic since a lot of people probably only deployed crowdstrike to satisfy their insurers' requirements.

It's the only reason we have it deployed.

I recall working on a PICK D3 system, which was a "multivalue" database. Each field could have multiple values, those values could have sub values, and a third level beyond that.

Values were separated with char(254), subvalues were separated with char(253), and the third level were char(252) separated.

It was... unique, but worked. And to be fair, PICK originated in the 60's, so this method probably evolved in parallel to the ASCII table!

This is the original reason for having /bin vs /sbin

The sbin directories are supposed to contain "system" (or superuser) commands, and regular users should NOT have those directories in their PATH.

This has been broken for a long time on every distribution I've looked at though.

I remember as a kid loading up the Encarta95 CD on the family 486, and the anticipation of what I could discover in the seemingly endless world of information that little spinning silver disc held within.

There is no contemporaneous equivalent.

Lulu is a good free alternative for Little Snitch