orev

There was a time before the Internet existed, and people were able to write programs. They reviewed the documentation, digested and understood the system as a whole, then worked on problems using that knowledge. That’s still possible today. When you hit a wall, you read through some more, try some things, and sleep on it. Often you wake up with the answer.

Not everyone is only copy/pasting from SO/Google/AI to know how to build stuff.

The vast majority of Linux installations don’t have a UI, they’re headless, and it was the same with Sun. I.E. the UI is irrelevant to the success or failure of Linux and Sun.

Linux took over the world because any licensing model that requires a per CPU license simply can’t work in a massively scalable situation like server farms and cloud.

They’re being used often in new construction areas. It’s just not likely that they’ll be retrofitted to existing areas due to needing more space than regular intersections.

The line of thinking is not about that $100 million bill, it’s about all the $100 million bills that come AFTER this first one.

As someone who got top grades in science classes, and a follower of science news for decades, I’ve never heard of temperature being a risk factor for cancer.

That said, it does make sense. Heat can cause damage to cells just like many chemicals can. I just don’t think many people connected the dots.

It’s still scanning (or at least listening to) all the other devices on your local network, like your phones, PCs, etc. It collects an inventory and if it ever happens to get Internet access, uploads that data.

They weren’t using RHEL. The title would be more accurate if it said “RHEL-based Linux”. They used their own build called Scientific Linux for a long time, then switch to CentOS. Then Oracle started aggressively poaching RedHat’s customers with Oracle Linux, which forced RedHat to start locking things down. One side-effect is that the life of CentOS 8 was dramatically shortened, and then RedHat killed the stable released versions of CentOS (9, 10, etc.). CentOS is now a rolling release “Stream” distribution, which nobody actually wants to use in production.

All this drama alienated many people who built their careers on RHEL-based systems, and created (either actual or perceived) instability in the RHEL ecosystem. And at the same time they started deprecating older hardware, some would say far too early. This is the “straw that broke the camel’s back”, as they said in the CERN presentation.

“You _will_ lose them”, as in, somehow Immich will do something to lose them (like making a mistake in a dedupe process which deletes the wrong things), or are you just saying you also need to keep backups?

It seems like we’re getting close, if not already there, to needing an official organization for this (i.e. the Turing Police).

I think you’re responding to the general idea of a relational database, not Postgres, and definitely not what’s in the article (DR;CA).

Postgres has built in data types and functions that allows it to work with unstructured json documents, like you would use in MongoDB.

When the audit happens, the auditors also consider if the policy meets the control objectives. If it doesn’t, you’re going to fail.

Glad to see fwknop mentioned. Back when the idea of port knocking emerged, there was a lot of criticism about it. Then this came out, and not many seemed to notice.

This was before WireGuard and Tailscale, so the main option for remote access was IPsec or OpenVPN, which are both more complicated than most people want to deal with.