Breathe, son.

Oh my god.

sh -c "$(curl -fsSL https://raw.githubusercontent.com/knadh/listmonk/master/

We absolutely need to stop this. Sure, I saw the disclaimer, but we need to end the normalization of running ANY black-box crap off the net. “curl|sh” needs to be laughed into exile for all our safety.

The easiest thing needs to be the right thing – common security saying

Then it’s

vim

As if that’s actually user-friendly or a positive experience instead of the worst thing to ever survive from the last century, crawling along on its rotting flesh and drooling on the pavement like some toxic residue from the vietnam war that it is.

In what asylum do you have the people willing to suffer vi and who also need a curl|sh ? Are they lazy or just misled as noobs into thinking vi is the only editor out the–

You guys, I just realized how vi masochists actually reproduce. It’s like zombies, guys, eating brains until the victim raises up another zombie.

And that curl|sh – does it invite supply-chain exploits? Ohhh, you bet it does! Best black-box script ever! Use this as a test for your security people – if they gauge this as a threat from within another threat, they pass. But, honestly, had it not been for the horrible spelling, I wouldn’t have thought to check further. \shrug. Mineshafts and canaries I guess.

As a sarcastic joke comment. Whoosh?

Apple and Google turn a blind eye to large apps.

I know people at both companies adjacent to compliance groups. They certainly do NOT turn a blind eye. They know if they mess it up once then they’re BlackBerry.

thru

Once this is edited, it’ll be a great document.

But wow, maybe ask a friend to do it for ya.

Tell me you don’t share a net with Macs without using those words.

Fucking GENIUS.

Forgejo actions is basically GitHub actions

That’s the problem. GH actions su-huck.

Biggest pain point was for our ops guy, who constantly had to stay behind to perform upgrades and maintenance,

This is weird.

Hosts selected for updates will be unavailable from 2100-2110 or so. Then they’re up.

They’re done by at/cron if they’re selected.

There’s no manual work if the monitoring system thinks they’re okay.

Gitlab-ce on-prem. Although that may now suck since they’re being bought out; and we all know how that went for redhat.

The PB&J sandwich is a valuable lesson. It needs to be taught to young and old alike.

have to check the source code

Use the source, Luke.

But yeah: disappointing. I just swapped out my Chef ZFS module because, looking at the source, it was incomplete in ways I didn’t want to rat-hole and extend while this other two-piece kit was there.

I should use the source earlier.

SUCKS that I’ve gotten a taste of project management and hated the absolute fuck out of it. I probably would’ve been decent at it otherwise.

Good PMs are rare, and precious. You could maybe give it another …

emails

oh, nevermind. :-P

I worked alongside some technical writers in the early post-y2k years at SCO. This was before they sued IBM for code misuse and died by a million legal and PR cuts, thanks to the ‘independent news’ site launched by a ‘recent ex-employee’ to reframe things then and rewrite history after.

We had about 15 tech writers in the company, which when I first arrived seemed like a LOT. I’d never met one, and I’d taken a single tech writing course in college as a filler and found it unchallenging work; so I didn’t value them at the time aside from filling a necessary role that your average nerd could surely fill. Then I saw their work; and it was amazing. It’s one of the product’s strong points, and 20 years later it’s still so head-and-shoulders above the similar offerings by others and since, that it’s a joy to read when I come across it.

Quite simply put, technical writers explain something in a logical, sensible way, where jargon doesn’t blind-side the reader and layout and language are consistent and easy. Hell, spelling is correct; which is a big win over 90% of the current stuff. Tech writers are writers as Lance L said, and thus know about adjective order, prepositional placement, the difference between ‘backup’ and ‘back up’ and all its similar terms; and of course know why e-mail and traffic do not get an S as nouns - ever - even if the popular kids make everyone say it without thinking.

It’s all simple-sounding stuff, and I was fooled into believing it was mundane; but when put together and written with an eye toward a common style it takes a stressful reader looking for a process or a parameter and induces calm for that brief moment required to get into the doc and find the sought-after bit.

Honestly, like the mentors we lost as a working society in the post-y2k bust when the c-suite cleared the ranks of things they didn’t understand, the loss of good technical documentation has a generational effect and will take a massive, sustained effort to reverse.

Docker always feels a little corporate.

I work in an ‘essential service’ environment for my main gig, where lots of checks and cross-checks need to exist. And it’s one that’s been under constant low-grade attack forever as it contains a LOT of tasty PII (personal info) and therefore has regs hammering it into shape. Docker cannot play here - and neither can Debian, actually, nor its derivatives - because it lacks the signed validation available in peer products sharing its space. As soon as the adults show up and notice a product with reduced validation is in place where a better one exists, the people owning that system have to write a life-cycle plan to upgrade, and it’s reviewed at an almost punitive frequency.

So, if you’re saying it’s a little too Corporate, I’m thinking you mean ‘suits and power lunches’ and not ‘large scale management of crucial systems and essential data’. True?

Are you confusing Alexa and Trump?

But jumping at the shadows is sometimes all the exercise we get!

Does the article say how the Alexa unit has absolutely no access control? Kids ordering dollhouses? Check. The news on TV triggering a response? Daily.

They can’t expect us to link our visa cards to something that doesn’t even know “this is little Billy” – actually it can discern people – “who should never be able to buy stuff” – which it can’t do.

The units are bad: no authorization and no auditing. Neighbor tried to order you 200 rakes as he rolled past your garage? You’ll get your f’n rake back, Dennis, just fuck off and don’t bug me every month.

Remember when sco used suse’s “seat license” wording and was totally hated - like “pitch forks and torches” hated - for it?

I’m only glad you weren’t suing someone for massive contract breach, for a value so large that a million dollar smear campaign was a drop in the bucket.

Sorry you ran into a mix-up like this.

*any email