Shaking my head my head while eating queso cheese, wearing a sombrero hat and drinking chai tea and while withdrawing money from an ATM machine.

Asahi Linux completely supports all the M1 Mini hardware.

But it does look the prices on these went back up because people use them for OpenClaw. 🙄

I run Asahi Fedora Linux on this hardware. It was a straightforward install and has been problem-free since.

M1 Mac Mini is quiet, fast, low power consumption and reasonably-priced used.

The log volume is dependent on which services are running and how they are tuned.

The high-res version would make a challenging 1000-piece puzzle.

I can’t tell if it’s a photo or masochistic hyper realism artwork.

So much detail!

I have a UPS that allows the server to survive an apocalypse of 15 minutes or less.

I agree it’s this, or the opposite: the stone is cool and the cat is hot. Either way, maximizing surface area for thermal transfer is smart.

Sometimes when I’m overheated on a summer run, I’ll find a brick or concrete wall in the shade and flatten myself against for a quick full-body thermal transfer.

Where does the $22 billion come from?

Store the secrets on a Yubikey. They are unstealable then.

Yubico has their own GUI app or you can wrappers for their CLI tool to use something like dmenu, rofi or Fuzzel to pick one.

The marketing mixes metaphors, talking about gardening, growing, curating… all part of sustainable process that includes plants dying.

It also uses words like forever and permanent.

Having content live forever is at odds with metaphors of the natural world, where things naturally die.

Clickbait headline.

SSNs have been understood to not be a reliable “secret” for years and were never intended to be one.

The solution has always been to quite treating them that way, not to repeat the same mistake of creating yet another database full of new SSNs which would also be quickly compromised.

How does it handle helm features that are not valid compose features? Silent failure or loud warning?

To explain how HAproxy and competing tools solve this:

Two servers are prepared to be the single reverse proxy, but one is active. They constantly communicate with a “heartbeat”. When the active one fails to send a heartbeat, the secondary executes the steps to become the active primary. When the primary’s heart starts beating again, it becomes active again.

So there can be a few seconds of downtime, but the failover is automatic.

Yes, especially if people use the “latest” tag, trusting whatever the container might be updated to do in the future.

I am using Navidrome and if it has significant bugs, I haven’t run into them yet.

Part of the app resides on the GitHub infrastructure, where GitHub stores, processes and displays results. So their costs are not zero.

But GitHub could take a “tax the rich” approach to pricing by charging enterprise customers more for self-hostingand leave it free for others.

A lot of open source is funded like that— most funding for a project comes from a very few companies and everything else uses it free or for very low donations or costs.

You have never had some family member experience a broken website that they needed to work but you were not around to fix it on the server side?

But companies like to make money default though.