Countries outside of the US are sick and tired of paying for what they see as untrustworthy American-dominated software-as-a-service (SaaS).

SJVn is so hit-and-miss for tech clue, but this resonated.

Canada is a country outside of the US. Can we get on the notion of independence and digital sovereignty yet, or are we still gonna chain our junk flotilla to this Titanic? And when it goes down, will Millhouse still be complaining about how slow we sink?

Absolutely this.

33 years in Linux, 30+ professionally, Unix+Linux security background in a past life at a fucking distro.

When I first install a new distro version, I do something very simple; maybe I configure a simple web page, for instance.

Usually the web server refuses to start, or something equally “so dumb it should have been seen in early testing and doesn’t even get to the challenge I set before it” stupid. If the distro can’t test something so basic, then I know they’re not prepared to consider selinux implications while maintaining or debugging the distro. I don’t need to blaze a trail the distro can’t be arsed to.

Then I mod away the config in my template and hope the distro can pull out their proverbial head in 5 years.

The easiest path needs to be the safest path

It’s funny how Ai is trying to lump itself into a datacenters-in-general issue or a general tech issue. It’s neither.

It’s not anti-tech: it’s anti-Ai .

seems unfinished

Can you still curse at them to get an attendant?

Meerly kats, ma’am. Just meer kats.

Knowing you have enough is absolutely satisfying. Musk doesn’t have it. Bezos doesn’t. You do.

This assumes everything is valid on the external. If one slop cluster feeds off another - a slopveyor? - then there is nothing external for the validation hall-monitor to compare against. They’re trusting another model’s output as if it were gospel.

YSK: as a mass noun, ‘spyware’ doesn’t need the indefinite article. We don’t say “a happy”, for instance, and we heckle those who say “a software”.

spend

Was the site built by coke-addled used-car salesmen on their break?

But the moment after showing LPs had this trope, it suggests album purchases – which had this trope.

I bought Finger Eleven, wanting an album of Paralyzed. I bought Mezzanine, wanting 10 tracks of Dissolved Girl.

In each case I got something else which eventually grew on me for the artistry it was, but in the moment I felt hoodwinked.

Anything container-free? We like iso27002, here.

setup

set up. “Setup” is a noun that lost its hyphen.

everytime

every time. Otherwise it’s not a word at all.

Ooh, good deal.

Too many sentence fragments. Stopped reading when I realized it wasn’t writing.

Not if I can help it.

composer/packagist has the exact same dependency security risks as node.js.

(Reposted)

Objectively, they all frustrate validation the same. When comparing with a SLSA3-compliant setup where every installed artifact has a signed checksum in a signed bundle from a signed resource on a signed repository, and the endpoint to this is readily available from something like authenticated SNMP into the single source of truth, they all tends to compare poorly.

The chart below completely ignores that Debs are consolidated into a single source of truth as well, and I feel violating SSoT should cost significantly because of dependency holes when artifact registry is incomplete, but SLSA doesn’t care about that part.

That’s difficult. Openssh is coded in C, not js.

The world-first part must be the wind-power thing.

We’ve had small offshore data centers for years, passively cooled but powered by nuclear energy.

(And if you’re still not getting the joke, let’s discuss how a nuke sub would cool its massive computing power. Big boats are like floating data centers; submarines even more advanced. )

why avoid Flatpak? I get snap or AppImage,

Objectively, they all frustrate validation the same. When comparing with a SLSA3-compliant setup where every installed artifact has a signed checksum in a signed bundle from a signed resource on a signed repository, and the endpoint to this is readily available from something like authenticated SNMP into the single source of truth, they all tends to compare poorly.

The chart below completely ignores that Debs are consolidated into a single source of truth as well, and I feel violating SSoT should cost significantly because of dependency holes when artifact registry is incomplete, but SLSA doesn’t care about that part.