aard

The problem with renewables is the fluctuation. So you need something you can quickly spin up or down to compensate. Now you can do that with nuclear reactors to some extent - but they barely break even at current energy prices, and they keep having the same high cost while idle.

So a combination of grid storage and power plants with low cost when idle (like water) is the way to go now.

I was referring to work setups with the overengineering - if I had a cent for every time I had to argue with somebody at work to not make things more complex than we actually need I’d have retired a long time ago.

Unless you are gunning for a job in infrastructure you don’t need to go into kubernetes or terraform or anything like that,

Even then knowing when not to use k8s or similar things is often more valuable than having deep knowledge of those - a lot of stuff where I see k8s or similar stuff used doesn’t have the uptime requirements to warrant the complexity. If I have something that just should be up during working hours, and have reliable monitoring plus the ability to re-deploy it via ansible within 10 minutes if it goes poof maybe putting a few additional layers that can blow up in between isn’t the best idea.

Everything is deployed via ansible - including nameservices. So I already have the description of my infra in ansible, and rest is just a matter of writing scripts to pull it in a more readable form, and maybe add a few comment labels that also get extracted for easily forgettable admin URLs.

Currently my mk4 is printing pretty much 24/7 with IS profiles. I’m applying some lubricant roughly once per week - sometimes I notice the printer starts making strange noises, mostly I notice when rods have zero residue between prints, and just add a bit.

I nowadays manage my private stuff with the ansible scripts I develop for work - so mostly my own stuff is a development environment for work, and therefore doesn’t need to be done on private time.

One thing I like about bluesky is that your identity doesn’t have to be tied to an instance domain - you’d still have issues if you want to change is later, but if you plan ahead and use your domain you can just move it between instances.

A lot of the Zen based APUs don’t support ECC. The next thing is if it supports registered or unregistered modules - everything up to threadripper is unregistered (though I think some of the pro parts are registered), Epycs are registered.

That makes a huge difference in how much RAM you can add, and how much you pay for it.

Funny timing, I’m currently going through a stack of Sun hardware in my garage to decide what to keep, and for what I’ll try to find a good home (or eventually dispose of it).

It has been a while since I touched ssmtp, so take what I’m saying with a grain of salt.

Problem with ssmtp and related when I was testing it was its behaviour in error conditions - due to a lack of any kind of spool it doesn’t fail very gracefully, and if the sending software doesn’t expect it and implement a spool itself (which it typically doesn’t have a reason to, as pretty much the only situation where something like sendmail would fail is a situation where it also wouldn’t be able to write a spool) this can very easily lead to loss of mails.

I already had a working SMTP client capable of fishing mails out of a Maildir at that point, so I ended up just doing a simple sendmail program throwing whatever it receives into a Maildir, and a cronjob to send this forward. This might be the most minimalistic setup for reliably sending out mail (and I’m using it an all my computers behind Emacs to do so) - but it is badly documented, so if you don’t care about reliability postfix might be a better choice, or if you don’t just go with ssmtp or similar. Or if you do want to dig into that message me, and I’ll help making things more user friendly.

Because it does JBOD if the controller supports it. Pretty much none of the controllers you’ll find in consumer hardware support that.

JBOD relies on an optional SATA extension, which most of your controllers won’t have.

That leaves you with RAID in the controller - which is a bad idea, as you don’t have much control over what is going on, and recovery if it fails will possibly messy.

You still might want to do something like alias pbtar='tar --use-compress-prog=pbzip2 to easily use pbzip2 - unless you have an ancient system that’ll speed things up significantly. And even if you don’t it’d be nice to use it for creation - to utilize more than one core the archive needs to be created for parallel extraction.

Here in Finland Fazer fills real egg shells with chocolate for easter, with the 4-pack also sold in egg cartons.

Bosch has a bunch that are quite useful for sanding in corners: https://www.boschtools.com/us/en/sanding-polishing-43817-ocs-ac/

I didn’t do enough testing with different materials for a conclusive answer - but that was my guess as well.

I should have 3 different glow filaments somewhere, one PETG, two PLA. Typically I preferred the PLA versions - they had a bit more uniform glow. The PETG one had brighter spots, but as it was mostly transparent individual spots were more visible than with the PLA prints.

Preordering made sense when games came in nice boxes, and you wanted to be sure to play it on the day of release instead of waiting for restocking. With digital downloads now which are not limited in quantity it is just stupid.

What kind of monster stores bananas in the fridge?

With lower voltage DC you can only set the house on fire. With high voltage AC you can set the house on fire and electrocute people. In a safety oriented company you’d try to limit the parts of the device carrying 230V (or, more generally: if your device has dangerous bits, you try to keep those bits in as few places as possible, as that limits teh amount of places you need to keep safe). Now obviously this has limits - like the mentioned bed size - but I don’t think we’re yet at a point where this should overrule safe design principles.

I haven’t seen a bambu printer myself yet - but given that the cable is undersized and not protected against side effects from bed movement I’d bet they also skimped on on making everything carrying 230V safe - in which case this is a cheaper design. I’m reasonably confident that a safe 230V heating design for a printer that size would not give you noticeably cost savings over a DC design, if at all.