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

Rundeck fits this space.

The very first HTTP based application I inherited was an internal system served by Apache on a Windows "server" using CGI to a "backend" written in VB6...

We would write the code in VB, compile the exe file (files? I forget), and FTP them to somewhere in c:\program files\

Pretty sure that system was a result of "when all you have is a hammer" from the previous IT manager.

The Australian government funds childcare. Every time they increase funding, the rates charged to parents increase by the same amount. Total conscience I'm sure.

My wife just stayed working full time because we need the money to afford our mortgage after interest rate rises. Almost 90% of what she earns goes to pay for childcare, and that's with her mother looking after our kids one day a week. If we had to pay for a full 5 days, it wouldn't be worth her working.

We still use pagers for emergency response alerting (Victoria, Australia). It's a dedicated, reliable alerting system that ensures the alert goes out between the emergency call takers and first responders.

It's reliable partly because it's so basic - it's a "one-way" broadcast network, and only operates at 1200bps (IIRC). They're not trying to build a network to serve hundreds of Mbps over duplex data connections so everyone can download their favourite cat pics. The network is built to cover 98% of the state by area, mobile networks cover less than that by population.

As a volunteer unit, we use mobile apps to augment our response (ie, hit green on our phone to indicate we're responding, red if you're not), but the primary alerting system is still the pager. The amount of people that turn their pager off then act surprised when they miss an alert because they don't get the difference is fun though.

he.net do free DNS, including secondary slaving. I've used them in a hidden master setup for a few years now for some domains, no complaints.

We had a bug recently where one of our internal bots didn't correctly parse usernames with hyphens in them, so instead of tagging @tom-jones, it would tag @tom

Sorry everyone randomly pinged by our bot.

My first job was supporting and developing order related systems for retail and wholesale (separate systems, but we operated both the wholesale and retail operations).

Wait until you start having to deal with Forward Orders, Back Orders, Special Orders, Cancelled Orders, and Refunds. Not to mention the General Ledger postings you have to make for each transaction too.

An "order" sounds super simple, but there are so many variations and corner cases.

You're probably right, but back then it was assumed you knew what you were doing I guess. The old idiom of "Linux won't stop you shooting yourself in the foot" was even more true of this system.

I can't remember the specific details now (almost 20 years have passed!), but the STKM table was effectively a performance/convenience data store. Every bit of information was available from other transactional data, but in order to actually have a chronological historical view of "stock movements", it was maintained in this central table.

No, I did the entire table. That helped me find corner cases and errors in my logic having such a bigger range of source data.

Yep, the entire table. I figured since I had to write it to do the day at a minimum, doing the whole table would help me find corner cases and errors since it was a much larger range of data

I was working on an old old old "ERP" system written in D3 PICK. It's a database, programming language and OS all in one with roots in tracking military helicopter parts in the 1960's. I was working on it in the mid-2000s.

It had SQL like syntax for manipulating data, but it was interactive. So you would SELECT the rows from the table that you wanted, then those rows would be part of your state. You would then do UPDATE or DELETE without any kind of WHERE, because the state had your filter from the previous SELECT.

It has a fun quirk though - if your SELECT matched no rows, the state would be empty. So SELECT foo WHERE 1=2 would select nothing.

UPDATE and DELETE are perfectly valid actions even without a state...

Working late one night, I ran a SELECT STKM WHERE something that matched nothing, then before I realised I realised my state had no rows matched, I followed up with DELETE STKM.

Yep, the entire Stock Movements table four the last 20+ years of business were gone.

The nightly backup had not run, and I didn't want to lose an entire day of processing to roll back to the previous night.

I spent the entire night writing a program to recreate that data based on invoices, purchase orders, stocktake data, etc. I was able to recreate every record and got home about 9am. Lots of lessons learnt that night.

Agree. Emergency vehicles don't automatically get a "free pass", there are separate rules that apply an exemption. So the question and rule, as written, says that the emergency vehicles do violate the rule IMO. In the real world, there would just be other rules that would apply an exemption.

(IANAL, but have been driving emergency vehicles for 15 years).

I'm doing the same right now. The incoming messages are coming from a radio network at 1200 baud, so I don't foresee capacity problems :D

This is great to escape untrusted/unknown local networks like a dodgy coffee shop or something. But definitely no protection against state level threats, etc.