Say Dukat, obviously.* One careless mistake should not erase his ceaseless dedication to the citizens of the quadrant.

Oh shit! No dip!?

I always thought it would be…them. Exaclty them.

How dare you throw shade at my Great Lakes Avengers! lol.

Rock on!

Edit: What I mean is - thanks for sharing, and I respect your efforts.

I plan to operate on expired certificates for two to four years, forcing all three of my users to click past a terrible warning.

Then I will automate my six day certificate rotation with Ansible (officially), but maybe actually with a stupid bash script in CRON (unofficially).

The real value is in the agility needed to update certs every six days.

Six days is still too long to leave a compromised key in play, but anyone who can rotate their keys every six days can probably also rotate their keys quite quickly if there’s a comprise.

I will study these. Thank you!

I’m not the OP, but I’m trying to figure out if local models are always painfully slow or if I’m missing something obvious in my tuning.

Stable Diffusion can whip up a picture in less time on the same hardware, than lama.cpp takes to decide to call an MCP function.

It seems like I must be missing something in my lama.cpp setup, but none of the guides I’ve read have clued me in to what I’ve done wrong.

Ollama performs similarly poorly on the same harsware, so I’ve probably managed to make the se mistake(s) at least twice.

Anyway, that’s the main thing I’m reading along for. Trying to increase my understanding until I catch my own mistakes.

+55653

Says everything I need to know about the change.