I was surprised by that, too. When I went looking for a way to decode them with RTL-SDR, I assumed it wouldn’t be parsing the audio but a narrowband data stream. TIL also.

Edit: It does kind of make sense with it being AFSK encoded in-band, though, or maybe I’m just so used to it being that way. I always thought the screeches were there to demand attention (and also be something that headend equipment can pick up and respond to). So it’s interesting they’re doing double duty as both an unmistakable audio cue to pay attention as well as containing the actual alert data.

Plus there are NOAA stations all over the country rather than centralized like the time signal transmitters. It was probably cheaper to do it in band at that scale.

That’s what I’ve done for years. Makes managing things much easier, and I run multiple APs (all with the same SSID/PSK) and you can just roam to the best one. One upstairs, one downstairs, one in the weird dead zone in my office, and one on the back patio (it’s not hardwired and uses the mesh connection for uplink).

These are all old Aruba APs running OpenWRT but that’s the plan for this Cudy Model. I may pick up a few more and just replace all of my trusty but very old Arubas.

I bought this one last month when it was on sale for $39: https://www.amazon.com/dp/B0BRK3CYY3

Haven’t deployed it yet, but it’s fully supported by OpenWRT. I would only be using it as an access point, though. My router is a USFF Optiplex with an extra NIC and runs OpenWRT.

Loops finally seems usable now. I tried the beta a while back and it was kinda “Meh” but it’s improved significantly since. And you can browse on the website now, too. I’m not into short form videos, but credit where it’s due.

Well, I do like short form videos, but I hate panning for the gems and just let my friends send me the ones that rise to top.

It’s so common for “anti-censorship” to be code for “Nazi-friendly” that I’m immediately suspicious of any platform that uses that as a selling point.

I’m similarly suspicious, but it’s not just code for “nazi-friendly” but also crackpots, maladaptives, etc. Rational people who read and say “anti-censorship” in this context know it means that it’s not beholden to corporate or government interests. But everyone else seems to want to interpret that as “I can say whatever I want! How dare you mod anything I say?! Freeze-peach, y’all!”

I wish they’d pick a different term for these non-corporate alternatives, but I don’t have a better suggestion to offer right now.

The irony of Lennart “let’s change everything about Linux because I know better” Poettering creating a company called Amutable is not lost on me.

But also, that tracks because now it’s “I know better so now you can’t change anything” which is pretty on brand.

The base system is stable. The only instability I really had with mine was the fingerprint sensor resetting every week. It would just stop registering until you turn fingerprint detection off, reboot, and re-enroll all of your prints. The second update they pushed seems to have fixed that.

Their default launcher could use some work. I replaced Minimal Launcher with a similar one that works identically. The problem with Minimal Launcher is it is hardcoded to certain apps. I’ve de-googled mine so I don’t use Google clock or calendar. Clicking the time or date in Minimal Launcher will only take you to Google Clock or Calendar (respectively) rather than asking what app to open or trying to detect the default app for that. I submitted a bug for that a couple months ago but so far no fix.

They also seem to only update their software (launcher, quick settings, keyboard config, etc) through system updates rather than via apps. You also can’t disable any of them either.

I also haven’t heard anything more about them supporting non-Googled or third party Android builds.

The hardware is the same AFAIK but they’ve put out two three software updates since I’ve had it. One added some extra features to the eink control utility and the second fixed some really annoying bugs with the fingerprint sensor. Both also included the system security updates as well.

There was a 3rd one a few weeks ago, but I think it was just a security bump. It wasn’t announced and just showed up. There may have been some tweak to the QWERTY keyboard utility because now the annoying bar that only indicated the ALT/Shift status at the bottom is no longer there and was happy to no longer see.

I was prepared for 6, but I’m good with 8. Thanks!

Same. It would definitely be my daily driver. I’m using the Minimal Phone now but have often found that I would rather have this same form factor with a regular screen, and the Communicator seems to basically be that. I am still deciding if I want to pre-order but I’ve set a reminder to do or don’t before the window closes.

According to the support ticket I put in a week or so ago, the bootloader will be unlockable which is great news.

The only thing the specs don’t mention is how much RAM it will have.

According to the support ticket I put in last week when I saw the first post about this, the bootloader will be unlockable. Or, at least that’s what they said. So here’s hoping we see nice debloated/de-googled ROMs.

At the very least, it should be immediately rootable with Magisk.

Love my deck … Kind of got side tracked gaming

You sound like me lol: Side tracked by the device’s primary purpose.

Sounds about right. I held onto my 16:9 OnePlus 3 until the battery completely gave out in 2023 or so. It was the perfect size, and I hated the 2:1 ones that came after. Tried a OP Nord N200 for about a week but returned it.

Daily driving the Minimal Phone now. It’s not the highest resolution by any stretch of the imagination, but it’s 4:3 and makes current phones look even skinnier than when I was used to 16:9.

The only thing preventing me from looking into this further is it’s yet another tall-skinny phone. I don’t know which manufacturer popularized that ridiculous aspect ratio, but I hate them and everyone who followed suit.

https://github.com/marytts/marytts

I’ve used MaryTTS semi-recently. It’s older but works well enough for my cases. I have it running on a server (locally) and my endpoints make a call to it and playback the returned audio file.

On Android, I use SherpaTTS which has good voices, but I’m not aware of a desktop/Linux option. It mentions using voices from Coqui which you linked, so I would guess that would be the way to go for desktop.

Yeah, I don’t know about pre-installed with Android that aren’t ad platforms masquerading as consumer hardware. I’d never use one unless it was supported by LineageOS or something. My comment was more “roll your own” in nature.

Maybe one of those HDMI “stick” PCs you can get? There’s x86 Android builds you can run or you can do like I did with my media PCs and boot into Openbox and just launch a fullscreen browser right to Jellyfin and control it from your phone. (My main setup uses Emby but should be able to do the same with JF).

I’ve actually got a portable Jellyfin server I take with me. Built on the OrangePi Zero 2W with a USB->NVMe acting as media storage (as well as the Jellyfin DB). It’s got several other services running as well as a second Wifi adapter so it can also act as a travel router.

For playback, I pretty much just use my laptop or phone but have thought about adding one of the “stick” PCs as a client for it.

What BIOS setting are you changing? Secure Boot?

Yep, that’s why I haven’t messed with Kubernetes either; way overkill for a homelab and especially so since I downsized due to soaring electricity costs here.

The only reason I gave up on Docker Swarm was that it seemed pretty dead-end as far as being useful outside the homelab. At the time, it was still competing with Kubernetes, but Kube seems to have won out. I’m not even sure Docker CE even still has Swarm. It’s been a good while since I messed with it. It might be a “pro” feature nowadays.

Edit: Docker 28.5.2 still has Swarm.

Still, it was nice and a lot easier to use than Kubernetes once you wrapped your head around swarm networking.