I’ve had this exact same gripe and can thankfully report that running EarlyOOM has fixed this for me.

I mean TDMA is also a perfectly valid solution.

Just needs an easier way to synchronize clocks. Maybe one (master) station could send out a sync word that lets all other stations start their clocks.

Opening the app for the first time on my Fairphone 5 (listed as unsupported) actually crashed the OS, but after that it seems to be working ok.

Closing out of the in-app gallery causes the app to crash. But that can easily be worked around by using some other gallery app.

I’ll be testing it for a bit to see how it fares against other HDR methods…

Well sorry for sending you down this rabbit hole, but thrusters get more efficient the less fluid is in their internal reserves ;)

There’s a table on the wiki page detailing how internal fluid reserve impacts thrust and efficiency.

I’ve omitted the fuel tanks in my newer designs. Tweaking the chemical plant output with modules is an easy way to hit the desired efficiency point. Although it’s probably not that easy when you have only one single shared chemical plant.

How quickly are you switching between recipes on the chemical plant?

Is it long enough for fuel/oxidizer imbalance in the thruster and how does that impact thrust efficiency?

I had the same opinion about spidertrons but with multiple surfaces and the changes to artillery in Space Age, I now find them extremely valuable.

Not to be pedantic but thats a displayshot and not a screenshot. ;)

Anyways your setup is much much nicer than the pile of spaghet I left on gleba to be overrun by stompers.

After filling up the turrets I start storing a couple of stacks of ammo in the ships inventory. Dumping that into the distribution system during flight makes things a little easier.

Why not set up backups for the Proxmox VM and be done with it?

Also makes it easy to add offsite backups via the Proxmox Backup Server in the future.

Out of curiosity I’ve let it rate Low<-Tech Magazine, a website run on an ARM SBC powered exclusively with off-grid solar power, and that only achieves 87% / A.

Link to results

It is, kind of. The plug is secured by 6 stops (or tabs) along each side. The positive pressure differential pushes the plug outwards into those stops.

To remove the plug you uninstall 4 bolts which allow the plug to go up and over the stops, after which it can hinge outwards on a hinge found at the bottom of the plug.

Source: https://youtu.be/WhfK9jlZK1o?si=dbUV1i2nNFcNixQh

Typst

You can use their online web-editor (similar to OverLeaf for LaTeX) or download the open-source engine and run it locally (there are extensions available for many text editors).

Compared to LaTeX I find it much more comfortable to work with. It comes with sane, modern defaults and doesn’t need any plugins just to generate a (localized) bibliography or include links.

Since Typst is very young compared to LaTeX I’m sure that there are numerous docs / workflows that can’t be reproduced at the moment but if you don’t need some special feature I’d recommend giving it a shot.

The development of Piper is being driven by the Home Assistant Project. That probably makes it one of the larger OSS TTS projects. Hope may not be lost yet ;)

https://en.wikipedia.org/wiki/Wikipedia:Unusual_articles

Seeing these little IT gems all over Lemmy always makes me smirk :)

I started out with WireGuard. As you said its a little finicky to get the config to work but after that it was great.

As long as it was just my devices this was fine and simple but as soon as you expand this service to family members or friends (including not-so-technical people) it gets too annoying to manually deal with the configs.

And that’s where Tailscale / Headscale comes in to save the day because now your workload as the admin is reduced to pointing their apps to the right server and having them enter their username and password.