Yeah the nodered flow on the target device is for handling shutdown(sleep) and status reporting back to HomeAssistant, so in HA the computer is a simple switch with on/off states

Oh neat!

I made a custom solution for WOL and remote shutdown using nodered and MQTT, but this is so cleaner than maintaining a custom solution

No they’re not, in fact Cosmic is almost ready for Alpha release (Sorry, couldn’t help myself)

You make a valid point.

One counterpoint does come to mind: Cost. The hardware to run it on ain’t cheap

(Im not up to date on the used market and the cut off point where old macs become unsupported and stop receiving software updates)

Had great success on Kubuntu. Set up the desktop to have two giant icons only: Firefox, and shutdown.

On Windows the constant popups for updating various components were causing much confusion Java, flash (back in the day), printer “drivers”, and of course windows itself would throw popups about updates requiring clicking buttons every time they used the computer, which was very infrequently, and cause them much confusion (“what does update mean” ?")

Meanwhile on Kubuntu all updates go “shhhh” in the background, and no more confusing “To shutdown, press Start”

This happens when a small project has 12 developers each scratching their own itch in their own time, not a team of 120 developers getting paid to work on the same itch 8 hours a day.

In the case of FreeCAD they’re actually starting to reign in and focus more now, and there are more contributors.

You might want to look up SMR vs CMR, and why it matters for NASes. The gist is that cheaper drives are SMR, which work fine mostly, but can time out during certain operations, like a ZFS rebuild after a drive failure.

Sorry don’t remember the details, just the conclusion that’s it’s safer to stay away from SMR for any kind of software RAID

EDIT: also, there was the SMR scandal a few years ago where WD quietly changed their bigger volume WD Red (“NAS”) drives to SMR without mentioning it anywhere in the speccs. Obviously a lot of people were not happy to find that their “NAS” branded hard drives were made with a technology that was not suitable for NAS workload. From memory i think it was discovered when someone investigated why their ZFS rebuild kept failing on their new drive.

Another option is subpaths: xyz.ddns.net/portainer

Just one open port, to your reverse proxy (nginx or other).

The client updating no-ip with your dynamic IP is independent of the reverse proxy software.

This sounds like a FOSS utopian future :)

There’s a few projects that have started towards this path with single-click deployable apps, you could even say HomeAssistant OS does this to some extent my managing the services for you.

I believe one of the biggest hurdle for a “self hosting appliance” is resilience to hardware failure. Noone wants to loose decades of family photos or legal documents due to a SSD going bad , or the cat spilling water on their “hosting box”. So automated reliable off-site backups and recovery procedures for both data and configs is key.

Databox from BBC / Nottingham University is also a very interesting concept worth looking in to:

A platform for managing secure access to data and enabling authorised third parties to provide the owner authenticated control and accountability.

Good explanation! And thanks for the CoreHunt suggestion :)

Probably more what MangoKangoroo and B0rax talked about, that enterprises can opt out of this telemetry, due to compliance or Intellectual Property protection.

So only the commoners get mandatory full-scale surveillance, Ehm I mean “ai enhancement”

I’m in this picture and I don’t like it

I third Proxmix

I run most stuff as Docker images inside a VM, but also a few services as LXC containers and some non-docker stuff in other VMs

One way is to make a new “entity”, that’s not actually linked to your previous temperature sensor. I’m not familiar with how to tie them together in a “device” like how ZigBee2mqtt auto discovery does.

So just add a new “sensor”/“entity”

  - name: "Sala_battery"
    unique_id: "temp_sala_battery"
    state_topic: "zigbee2mqtt/temp_sala"
    value_template: "{{ value_json.battery }}"
    unit_of_measurement: "%"

Use MQTT Explorer to listen to your ZigBee2mqtt broker topic “zigbee2mqtt/temp_sala” to get the exact field name (battery, battery_state or some such)

Sounds like the FDA should be involved here somehow…

How much of this is Spotify’s fault and how much is the major record labels sitting between Spotify and the individual artists?

And is there a better place for us consumers to go and vote with our wallet? Ideally somewhere that isn’t one of the 5 major tech giants that control everything

That’s brilliant! I always forget KDE Connect also works fine PC <–> PC, not just PC <–> Mobile

+1 for SSH and FileZilla (or WinSCP)

That’s very strange, which distro and GPU was this? So I don’t recommend that to anyone?

I’m assuming the GPU in question was Nvidia, since AMD and Intel make their driver opensource and baked in to the kernel. Sadly nVidias latest kernel (535) has been troublesome, so I’m still on the previous 525. nVidia is about to release 545, which looks to be very promising.

Luckily on Ubuntu changing driver is as easy as opening the Additional Drivers application, selecting the driver version, hit apply and reboot. PopOS, Bazzite, and a few others comes with Nvidia drivers preinstalled.

Best of luck if you try again in the future

The visual style is like a cartoonified version of the Ori (and the Blind Forest) visuals. It’s very pretty.