I would use their LXC install, it’s much more flexible. It does not need to be local but it does simplify things like email. I had to put a bit of effort into getting it to be able to connect to IMAP mailboxes to process, but it wasn’t any more than just asking it to get the necessary libraries etc. But things like that are why using it as an LXC is a better choice. It might be able to do that as a docker, but there’s potential problems with network connectivity and docker in docker issues.

You can also firewall that LXC off without having to mess up your own workstation, as well as snapshot it and back it up.

And the first thing I would do is have it keep token budgets when you build tasks, and report it’s token use to you every hour or two. It takes some time to learn how to structure reminders and task processing to not create loops that eat up scads of tokens. Don’t ask me how I know.

But holy hell, can it be useful.

zfs.rent

I had a pig named Porkchop.

She had great taste.

I set up Pulse recently and the ease of setup and great UI/UX is impressive. Really liking it.

Of course, there’s some AI bullshit if you want to opt in, but it’s not enabled by default.

I tried it a couple years ago and it wasn’t very successful. But maybe that’s changed.

The other server sends again until it times out? Never been an issue, that’s just how email works. Most SMTP servers will attempt for a few days if they know the MX is valid. Besides, I’ve never been out for longer than an hour or two.

Seems really low. I run it on a docker LXC with Nextcloud and bunch of other stuff, on 8 cores of an ancient dual Xeon Dell. I never seem to have to deal with latency on it.

Mailcow-dockerized. I’ve used it for nearly a decade, it’s been flawless. Very easy to set up with the admin webpage and has a webmail client, or use Roundcube with it.

Make sure you have your DKIM, SPF and Dmarc records in order and tested against MXtoolbox before you start.

Frigate is painful to set up. It won’t just go out and query the onvif capabilities so you have to try and figure out its RTSP url manually and ptz support is primitive. Its low resource and stable once you manage to get it to work.

Blue Iris is much easier and more capable, but uses Windows, and its a resource hog, and its paid. But if you get past that, BI is really good.

That’s a real bitch if you’re running watchtower and have the latest tag set. If you aren’t watching this drama, it’s an easy pwn for whoever took it over.

Docker Hub needs to get their shit together.

• hire a Canadian driver

I do OK with faster-whisper for transcribing, and I built a wyoming container for pocket-tts that does pretty good local TTS but I am running it as a docker on a ryzen machine (no gpu) so YMMV. Pocket-TTS seems better than Piper IMO, it’s certainly faster for local TTS if all you’re using is CPU.

I’ve been looking for a MCU that has enough oomph to do some noise cancellation onboard and I ordered up a couple of these in the hopes that the onboard NPU would be useful for that. It also has a speaker output and onboard mic. Price was right for 8GB of EMMC and 256MB of ram.

Are you doing anything special for the microphone(s) and noise cancellation? I’m leaning towards making my own satellites as I’d like a half a dozen or so and the PEs are more than I want to spend on the project.

It is much more accurate if you use the pump. I tried just measuring the pressure in the tube from the water column, it was all over the board and the resolution sucked, probably 10X worse. Using the pump fixes that because you aren’t just measuring how much the water compresses the air, you’re measuring exactly what pressure it takes to push out the bottom, which is exactly the water column. It doesn’t take much of a pump if all you’re pressing against is a few feet of water. Something like this: https://www.aliexpress.com/item/1005009288427024.html

I’d just tie it to a heavy nut and drop it in the well. I probably wouldn’t even measure it, just calibrate on some known water levels and watch it for a while.

If you want an accurate measurement, you can put a tube that exits below the lowest water level you expect. Put a pressure sensor like an MPX2102 and an aquarium pump on the tube. When you turn on the pump and it starts bubbling out the tube at the bottom, the pressure you measure on the sensor will be relative to the height of the water column above the tube opening. 1"wc is approximately 249.082 pascals or 0.0361263 psi

I use this method on my brewbot for measuring the amount of water in the kettles for strike and sparging. It’s accurate to within a 100mL or so, at least with the ADC I’m using on my controller. You might need a slightly different sensor depending on the over height of water column you plan to measure.

Fixed.

Thanks. Yah, afaik pocket-tts hasn’t built anything but English yet. It’s pretty new.

Good to hear you got it to build. The base project seems to move fast so I just set this up to require a local build which will pull the pocket-TTS current code in directly.

I guess I could post a GHCR image, but I’ve never done that. I just build my own images, it’s pretty quick and then they’re up to date.

Thanks, I forgot to link that. I guess it’s in the README in any case.

What a time to be alive.