Responded to @janboddez:

@janboddez There are a few individuals and companies who are batch-submitting “vulnerability reports” that rely on DB read access. Plugins storing any kind of secrets in WP options are all targeted.

I do understand the benefits of encrypting those secrets but that would require asking site owners to update wp-config.php which is the only “safe” place to store secrets in WP. Imagine each plugin asking for its own constant…

Something enabled the default webserver on ports 80 and 8081 of our home QNAP NAS which prevented the my reverse proxy container from starting on the same port. Maybe enabling home folders does this?

Responded to @kasparsd:

If only I could count 😅 — it is clearly 6 full days which brings it to 6.6Wh / 6 days / 24h = 0.046W or 12mA@3.7V on average.

It took 5 days for my Heltec Lora v3 #meshtastic router node to use up 6.6Wh of one 18650 cell at 5% air utilization rate (one telemetry message per minute). That brings it to 6.6W / 5days /24h or 0.055W (15mA@3.7V) on average.

Importantly, this node was also powering a #INA219 sensor which was doing the power measurements every minute.

Now I'll be doing a reference measurement without the INA219 and with zero telemetry.

Responded to @adingbatponder:

@adingbatponder It relies on the Web Serial API https://developer.mozilla.org/en-US/docs/Web/API/Web_Serial_API so you could check the browser console for any errors or warnings.

Finally added a basic dark mode to my 10 year old hand-rolled WordPress theme with no CSS post-processing.

Responded to @kasparsd:

Turns out `tar` can’t incrementally update encrypted archives (makes sense), and it also can’t update an unencrypted archive with just the changes so you’re responsible for ensuring the full chain or snapshot archives which isn’t feasible.

Block-level snapshots are nice, though. The network transfer is more consistent when compared to file level transfers.

Has anyone tried backing up #homelab LVM snapshots using `tar –listed-incremental` to a network attached samba share? https://www.gnu.org/software/tar/manual/html_section/Incremental-Dumps.html

I’m comparing that to an older version of #restic which doesn’t support compression, yet.

Couldn’t get the #beelink EQ12 (n100 CPU) to run from a 30W PoE splitter and a TP-Link TL-SG108PE switch. The cheaper 12V/1.2A splitters would actually turn off while this one stayed on and wouldn’t boot. Didn’t have a monitor to check the console output.

“Nearly the entirety of every Mastodon server, every post, every reply, is ephemeral. When a Mastodon server shuts down, all its posts disappear from the surface of the web, forever.” — that’s why #POSSE is so great! https://fed.brid.gy/r/https://tantek.com/2024/046/t1/the-ephemeral-web

Here is a hot take — instead of investing in AI, @mozilla should be selling hosting services, domains and email hosting, and stay true to the open web stack. Imagine how well you could pair those with Firefox similar to how Chrome does. https://mozilla.social/@mozilla/111896572632380551

Responded to @oivaeskola:

@oivaeskola Yes, since HomeAssistant supports running the full “operating system” inside Virtualbox (same as Hass.io) so you can install all the add-ons (basically Docker containers with some meta data) through the built-in tooling. You will need to forward the serial port to Virtualbox machine for the zigbee dongle, but everything else should be possible to configure from the UI.

Responded to @kasparsd:

@oivaeskola Are you planning on running HomeAssistant on macOS inside Virtualbox? In that case you can run the official MQTT broker add-on https://github.com/home-assistant/addons/blob/master/mosquitto/DOCS.md and MQTT component https://www.home-assistant.io/integrations/mqtt/ alongside the zigbee2mqtt add-on https://github.com/zigbee2mqtt/hassio-zigbee2mqtt#installation