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.

And please don’t understand this the wrong way.

Ibis seems like a really cool project but with it being roughly half a year old me and many other people here simply have never heard of it before.

Including even a single short sentence describing what Ibis is in this and future posts helps us find projects that we care about more easily.

And we obviously care about Rust projects, otherwise none of us would be here.

Ibis is a federated online encyclopedia similar to Wikipedia.

This should be the first sentence of the post body.

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.

That’s for a single one but at tens of MW even a bunch of satellites isn’t going to get solar panels to produce an appreciable amount of power.

This video goes into the details of what kind of performance we can expect from the constellation

No the observed power on the ground is on the order of mW/m².

Comparable to moonlight and so far no one has classified that as a weapon.

As always with these revolutionary startups, be careful with what you believe:

EEVblog 1637: Solar Freakin’ Space Mirrors! - Reflect Orbital DEBUNKED

At least this one is actually possible and doesn’t attempt to defy the laws of physics.

Also crashes for me with 0.2.1

Found this comment with some links. Couldn’t find anything from an admin during my short search.

The exact same problem arose for Voyager users in March when Voyager dropped support for Lemmy 0.18.

For some people logging out and back in has helped but I’ve seen multiple beehaw users state that this doesn’t work for them.

This seems to be because beehaw is intentionally staying on an old Lemmy version.

Not sure how the Dev wants to handle this since they’ve got enough work on their hands and this issue should resolve itself once beehaw upgrades.

For now your best bet is to try re-logging and if that doesn’t work to roll back to a previous version of Eternity.

Always mocking Dr. Daniel Jackson. Poor guy

Additional information regarding Home Assistant:

The sun component (which should be enabled by default) already computes the sun position for you.

Elevation and azimuth are available as standalone sensors sensor.sun_solar_azimuth (might be disabled by default) or as attributes on the sun.sun entity.

I don’t have any experience with it but this might do something along those lines(?):

https://esphome.io/components/binary_sensor/ble_presence.html

Seems like you can just add it to one or more of your existing esphome devices.

Cushy is an experimental Graphical User Interface (GUI) crate for the Rust programming language. It features a reactive data model and aims to enable easily creating responsive, efficient user interfaces. To enable easy cross-platform development, Cushy uses its own collection of consistently-styled Widgets.

Indeed

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

Can’t exactly remember which car it was but some of the early and smaller EVs didn’t necessarily come with a navigation system. Think along the lines of Chevy Bolt or Nissan Leaf.

Not OSM or Open Source but “A Better Route Planner” (ABRP) was one of the first good EV routing apps and got pretty popular.

Especially early on it was often smarter than the built-in routing systems if the car even had one.

Also available as a website: ABRP

If you have such a system up and running already you could try to modify it before ripping it out and starting from scratch.

Borrowing an idea from the machine learning approach you could additionally take the difference in average outside temperature yesterday and the average forecasted outside temperature today. Then multiply that by a weight (the machine learning approach would find this value for you but a single weight can also be found by hand) and subtract it from the target temperature before the division step discussed previously. Effectively saying “you don’t need to heat as much today since it will be a little warmer”.

I fear that’s about all you can do with this approach without massively overcomplicating things.