badlotus

An alternative to MusicBrainz Picard is Lidarr. No sonic analysis but it can organize and rename your library among other things.

Picard is the better option for music organization though.

I found an informative post about a related issue that might be of some use to you. Sounds like DHCP or Network Manager may be rewriting your systems-resolved.conf.

https://joshrnoll.com/my-tailscale-dns-woes/

Have you tried deleting /etc/systemd/resolved.conf and restarting the service with systemctl restart systemd-resolved?

Did you undo the reverse path strict filtering your guide suggested?

net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1

Above is what the guide suggests to force reverse path strict filtering. Try setting as shown below:

net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.all.rp_filter = 0

According to the guide, “By default, these are set in /usr/lib/sysctl.d/50-default.conf”

Fair points! I’ve been tinkering with Homeassistant for a while now. The community has come very far so I’m hopeful that more advanced features will be added as the user base grows.

Yes, the voice recognition is decent. I mainly wanted a way to control some smart light switches without using a Google device. If you’re looking for something more advanced I don’t have any experience using his tool in that use-case.

Have you heard of Ollama? It’s an LLM engine that you can run at home. The speed, model size, context length, etc. that you can achieve really depends on your hardware. I’m using a low-mid graphics card and 32GB of RAM and get decent performance. Not lightning quick like ChatGPT but fine for simple tasks.

Ollama

Have you heard of Homeassistant? It’s a self-hosted smart home solution that fills a lot of the gaps left by the most smart home tech. They’ve recently added and refined support for various different voice assistants, some of which run completely on your hardware. I have found they have great community support for this project and you can also buy their hardware if you don’t feel like tinkering on a Raspberry Pi or VM. The best thing (IMHO) about Homeassistant is that it is FOSS.

Homeassistant Voice Control

Here’s an article with a bit more detail… but I’m still unclear whether these backdoor commands are hardware circuits or firmware logic.

Bleeping Computer: Undocumented "backdoor" found in Bluetooth chip used by a billion devices

Some of this was written by ChatGPT. Good eye.

Think of Docker containers like lightweight, portable mini-computers that run on your actual computer (the host). Each container has everything it needs to run an application—like code, libraries, and dependencies—but it shares the host’s OS kernel rather than running a full OS itself.

Containers vs. the Host System

• Not a full OS: Containers don’t have their own separate OS but use the host’s OS kernel. They do, however, have their own filesystem and isolated environment.

• Like a sandboxed app: A container is more like a self-contained app that has just enough system components to run but doesn’t affect the rest of your system.

Keeping Containers Updated

You do need to update containers separately—updating the host system isn’t enough. Here’s why:

1. Containers use images: Containers are created from images (like templates). If the image gets outdated, the container running from it will also be outdated.

2. Rebuilding is required: You can’t “patch” a running container like a normal program. Instead, you must:

• Pull the latest version of the image (docker pull my-image:latest).

• Stop and remove the old container (docker stop my-container && docker rm my-container).

• Start a new container with the updated image (docker run -d --name my-container my-image:latest).

Automating Updates

To simplify updates:

• Use a container management tool like Docker Compose, Portianer, or Kubernetes.

• Watch for updates to base images (docker images to list images and docker pull to update).

• Set up an automated pipeline to rebuild and deploy updated containers. There are tools like Watchtower that will automate this with minimal effort.

In short: Updating the host OS won’t update your containers. You need to rebuild and restart containers with updated images to keep them secure and up-to-date.

Note for comments below: If you are trying to customize a docker image, you must build a new image. This is done through “dockerfiles” that instruct the docker engine what commands to run on a base image to create a custom image. For instance, one could take a simple Linux image like Alpine and use a docker file to install NGINX and make an NGINX image to create a reverse proxy container. In many cases you can find images that have been published that meet most basic needs so building images is often only necessary for advanced docker implementations that require special customization.