

I can get notification to ntfy, but I’m not sure if the app is certain to blow my phone up until I notice it, which is my goal. Frankly, if I could trigger the Presidential Alert, I would do that.
I can get notification to ntfy, but I’m not sure if the app is certain to blow my phone up until I notice it, which is my goal. Frankly, if I could trigger the Presidential Alert, I would do that.
The application isn’t 100% likely to stay active in the background it seems. I tried to program one myself but there’s a lot of bullshit going on in background apps in Android that I’m not familiar enough with to trust that I can do any better.
Any suggestions for services that do that? I like the idea, I’d actually get a few different phones to ring if some of the alarms were to get triggered.
This is my summer solar system. I like to winter in the Antares.
There is a guide in the Mail cow docs on integrating Roundcube, that’s the client I use for my stack.
I mean, it’s bcachefs. It’s far from production ready.
If LO doesn’t work for her, there are other options like OnlyOffice and WPS Office as well.
I’m not sold on GLinet’s implementation of OpenWRT. I have 3 of them in production, and all three need regular reboots to stay working. I like the VPN interface they have and the ability to get to the underlying Luci interface, but I’ve found just flashing my own device to have a more stable and deterministic result.
I can’t speak to VLANs in specific, because I haven’t trusted them enough after seeing the rest of it to use it anywhere critical enough that I use VLANs.
I’m trying to figure out how to add it to Mailcow Dockerized and hook the existing containers. If I sort it out, I’ll probably PR it to Mailcow. I think it would a nice addition to start to build out a network that isn’t susceptible to the same spam attacks as regular email (yet).
I remember as a kid I set up one of the first private Echomail nodes as part of my RBBS bulletin board. UUCP was a big part of that, as I was the hop for other nodes coming onboard in my area. I added another half-dozen modems eventually just to handle the email traffic, then had to offload it to a university because I didn’t want to have to charge for the traffic and it was getting too big to handle. But it was pretty interesting at the time.
Wayland support in Mint is experimental, it’s not worth your time if you’re playing games. X11 is on maintenance-only life support these days.
I ran WoW for years on Arch until I stopped playing a few years ago. IDK what the experience is like these days, but it was fine then.
Personally, since I don’t like the runaround to install things on Bazzite, I would use Nobara or just vanilla Fedora with your own drivers. You can use Btrfs Assistant to set up Snapper snapshots and boot entries if you want, but I’ve never seen a Fedora update fail in any critical way. Frankly, I’d be inclined to just go with vanilla Fedora since GloriousEggroll is a busy guy and updates aren’t very up to date on Nobara IME.
Yah, and it has it’s limitations, but it’s far lighter than electron IME.
I’ve been using Flutter, I like how it’s cross-platform, mostly. I’ve generally built things for Android, but the desktop (Linux and Windows) and web versions usually compile fine with no tweaking. Couldn’t speak to the iOS versions as I can’t be arsed to jump through Apple’s hoops. You can make a nice looking app with it for whichever platform you’re targeting.
It’s very well supported, lots of examples, well documented. Not as much out there as Python for examples and troubleshooting, but not bad.
I mustn’t be communicating well, but that’s fine.
OK, yah, that’s what I was getting at.
I was getting more at stacks on a host talking, ie: you have a postgres stack with PG and Pgadmin, but want to use it with other stacks or k8s swarm, without exposing the pg port outside the machine. You are controlling other containers from interacting except on the allowed ports, and keeping those port from being available off the host.
I assume #2 is just to keep containers/stacks able to talk to each other without piercing the firewall for ports that aren’t to be exposed to the outside? It wouldn’t prevent anything if one of the containers on that host were compromised, afaik.
“All your containers are belong to us.”
Not as confusing as Debian though.