They got bought out… By WDC.

I’d recommend a solid backup client. This isn’t something you want to find broken when you need it.

Kopia is what I use, and it supports local (LAN) targets, as well as cloud storage if you want 3:2:1 for some or all of your data. Good luck!

Theres a Romm app in ports you can use for this.

I was interested until I saw the crypto stakes to vote on changes baked in.

Similar setup here with a 7900xtx, works great and the 20-30b models are honestly pretty good these days. Magistral, Qwen 3 Coder, GPT-OSS are most of what I use

Yeah, similar sized environments here too, but had good experiences with Ansible. Saw Chef struggle at even smaller scales. And Puppet. And Saltstack. But I’ve also seen all of them succeed too. Like most things it depends on how you run it. Nothing is a perfect solution. But I think Ansible has few game breaking tradeoffs for it’s advantages.

Wow, huge disagree on saltstack and chef being ahead of Ansible. I’ve used all 3 in production (and even Puppet) and watched Ansible absolutely surge onto the scene and displace everyone else in the enterprise space in a scant few years.

Ansible is just so much lower overhead and so much easier to understand and make changes to. It’s dominating the configuration management space for a reason. And nearly all of the self hosted/homelab space is active in Ansible and have tons of well baked playbooks.

I’ve seen this one, is it the one you meant?

https://tineye.com/search/4e3f5f9f6c1a9805fe0b42068e45f3e47bc8ab8f?sort=size

What’s on your mind?

What controller?

Imagine when a titanosaur died.

This is correct for a given transaction, but there’s no consensus needed to open a Bitcoin wallet. That is usually just a private key in an encrypted envelope.

Alabama’s state slogan is “Thank God for Mississippi”, because they can at least point to one place where things are worse.

Are ya p-hacking, son?

The life and times of a software developer.

Annoyed or excited. Call it “stimulated”. Also often happens when they see a toy or a pounce target.

Usually with domestic cats the ears being in a relaxed ‘up’ state show this cat is annoyed but not truly unhappy. Maybe even trying to wriggle away.

Generally if you see highly dilated eyes and ears back, the cat is about to attack or pounce.

However I’ll caveat that second part with the fact that it depends on the cat. I’ve seen cats maul from a submissive/passive position with ears up and eyes nearly closed. Like humans, every cat is different and every situation is going to be unique. They’re intelligent animals with unique personalities and nature/nurture, which is why they’re such excellent companions.

Modern transistors aren’t just silicon though. The silicon is doped with various materials, presumably gallium, boron, arsenic, phosphorus, and cobalt, among other elements.

https://en.wikipedia.org/wiki/Doping_(semiconductor)

I mean, effectively superdeterminism’s natural conclusion is that time is an illusion. Everything that will be was already fixed at the start of the universe.

But turning this back on itself, what’s the proposed mechanism for quantum wave collapse at superluminal speeds?

Our understanding is fundamentally flawed, but thankfully the math works!

Happily!

So, first epoch time. It’s a pretty robust standard, covers many use cases, has few edge cases… but it’s specifically for machine usage, since it’s not human readable and it’s not reversible into the past (pre-1970).

ISO 8601 (depending on the annum), by the text of the documentation, these are all valid dates:

• 2007-04-05T14:30
• 2007-04-05T12:30−02:00
• 2007-04-05T14:30Z
• 200704051430
• 07-04-05T14:30
• 2007-95T14:30

Etc.

RFC 3339 (& RFC 9557, it’s newest modification) is actually a subset of ISO 8601 and is far more prescriptive. For example you must have a timezone designator. You must have a separator between the date and time. You must use a dash between date elements and a colon between time elements. You can easily add standardized subseconds.

• 2007-04-05T12:30−02:00
• 2007-04-05 14:30Z

This means that RFC 3339 is much easier to parse and use by both machines and humans.

This page (reddit, I know…) has a great summary, and so in the interest of knowledge and attribution I’ll link it: https://www.reddit.com/r/ISO8601/comments/p572xy/rfc_3339_versus_iso_8601/

This website allows you to more directly compare the two interactively. https://ijmacd.github.io/rfc3339-iso8601/