Careful. The yaml cult will come after you in a long and formless column, and only self destruct when one of them is a step too far to the left.

It’s okay to still use a hyphen between ‘load’ and ‘balancing’. As a bonus, what you write would then be English, too.

Is that the same as prosody.im ?

That’s the one I’ve been looking at. It seems to be easy, but I haven’t had time to look into it fully.

feel free to join and open a ticket in our Discord community

Yeah, honestly, kinda fuck off a bit.

true for open source software though, a lot of open source devs are mini dictators

When I ran my open source project, I was discerning as to what code I’d accept from people.

Does that make me a little dictator if I don’t want to then maintain shit code from someone who doesn’t know what a comma splice is, like above?

Sorry if you do code better than you write.

Flatpaks are a cancer. Got anything else?

I’m running ZFS at two jobs and my homelab.

Terabytes and terabytes. Usually presented to the hypervisor as a lun and managed on the VM itself.

I don’t run proxmox, though. Some ldoms, some esx, soon oVirt.

In 5 steps it violates ISO27002 3 times.

I’d say any setup result is purely accidental on the way to something far more exciting.

because the another backdoor

You’re gonna want a cat-scan.

I’d look over the server install if the process had docs.

I looked at matrix but the server setup was janky – enamoured of the current mayfly shine tools, and when I saw mumble install cleanly on my tiny arm box it was a sea change. No longer have the tiny arm box but I still run mumble.

I’d be super happy if it and its polite codecs were brought into the fed but I haven’t been paying attention.

Yay mumble!

And I agree: it’s better. I think it’s faster and that, IMHO, is where the power is. It can look boring like a hammer as long as it’s intuitive … like a hammer.

deleted by creator

a […] infrastructure

The uncountable becomes countable.

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.