I’m kinda planning on teaching my team
I’m not going to deal with their git issues for them.
These two statements contradict each other.
I’m kinda planning on teaching my team
I’m not going to deal with their git issues for them.
These two statements contradict each other.
Ha ha
Under-complicated -> over-complicated -> under-complicated.
There’s a ‘just right’ that I think you skipped through.
LibreOffice 25.2 Released, This is What’s New
In addition to the comma splice?
Whatever makes the fascism facilitators sleep better I guess.
Lat I checked, it was 40w idle for me on the kill-o-watt. Spinny rust and all!
just
Uh oh. Red flag.
gotta pop the panel cover off,
This may be where the rental agreement is broken. Define ‘pop’ . Two hands and a tool? Clear it with the landlord first. The company running the 400-unit building where I am now is gonna say F No.
Yeah. I got a pro managing it.
Evaporative clay-pot coolers are also top-load for efficiency.
Without space between the contents, though, they freeze in phases and it affects how they come out. Watch out or just keep air gaps.
Are both immich and photoprism container-dependent, or just immich?
(If they fail 27002, they’re a hard no for me).
LDAP server is also helpful, even though you can just use the file backend of Authelia.
Samba4ad was easy to set up and get replicating. Switch over soon as you can.
Debian will have snaps and flatpaks and all the same insecure black-box drek.
Given how much they violate ISO27002, I can’t see them ever being run in a regs-compliant shop.
From a security standpoint? Not even close. From a software-release validation requirement, not even in the same galaxy. If they look the same, it’s only due to Clarke’s law.
If only they weren’t flatpaks. Ask a release engineer about importance of artifact validation and single source of truth if you don’t know why that’s a risk.
everyday
every day
I can’t use signal.
Next?
a big ask
Don’t forget: once you’re off the car lot, you don’t say ‘the ask’ any more. “A big request” happens to be English and also valid for the context.
The crucial point is that the people who can work on the kernel now itself are
The moment we get rust in there, the people who can work on the kernel reliably as a whole are
That’s a much smaller group than the one above.
Here’s the point: THE SAME ISSUE would arise if it were D, or some kind of compiled python, object-oriented bash static objects, if that existed; or anything. Whatever the other language was, it’d present the same risk.
Rust people: it’s not about you. It’s about splitting the codebase.