Maybe about 18 repeaters all over the house.
Thanks. All the plugs and bulbs are routers, so I have about 20 routers in the network, so that shouldn't be an issue.
I've repaired an item or two multiple times the last couple of days.
I could be close to the limit, I have about 46 devices on the ConBee2. But it is a new problem, I would have thought this would be happening as soon as I started nearing the limit, not months after it.
I have not added anything new in the last couple of months.
This reminds me of the Docker issue they fixed in Omarchy recently. Basically you could get root through the docker socket, because the default user groups included the docker group.
Almost true.
It is pretty picky, as it expects a certain folder structure to get all the info correct when importing. But it is fairly easy to go in and manually "fetch" the correct metadata from one of the metadata providers (Amazon, Google Books, Open Library etc). It's a chore if you have big library with many different structures, but doable if you don't want to rename all folders.
And you can check the shasum of the binary to see if it actually matches that provided by the developers of the application.
A malicious PKGBUILD, which is what is being talked about, you would see that it downloads a binary that does not come from the developers and so you should not install that.
If the attack happens on the developers repo, not even Linux repository packages would be safe at that point (eg, the xz heist).
Rarely, but I check the PKGBUILD to see if the binary is what I expect it to be.
But if you read the PKGBUILD, you would see that it downloads and runs a black-box binary and should therefore not install it. It's a little harder with PPAs I think. The build files are not so easily found.
CPU usage on the server is about 5-10% (it does loads of other things too), so home assistant is not using much.