and what happens then? land on a blacklist? for some that’s the best outcome

you whisky couldn’t solve tarpits completely. they may hold up the scrapers for less time, but they will still do that for the amount of the timeout

they cannot block what is internal. google does not need to be aware of your internal activities anyway

you can selectively mark mails as read that don’t need attention anymore, and keep as unread those that do. how would you do that with ntfy, or messaging services? at most you can mark unread a whole topic or chatroom

and no, I don’t want to make gitea issues for every single alert. (though… why not?). it would be very fragile anyway I would assume

The good news is this still works despite no updates it does everything it used to. There is almost zero reason to update any working NAS if it is behind a firewall.

if all users and devices on the network are well behaved and don’t install every random app, even if from the play store, then yeah, it’s less of a risk

you don’t need to expose it. set up wireguard and have fun much more safely

sorry what, it can keep a location history? how?

sorry what, it can keep a location history? how?

that’s how it works on desktop too regarding DNS, but when it receives a response from a new IP, it should send future traffic there as I know

but I found I spent way too much time trying to manage RAM and tuning it,

I spent none, and it works fine. what was your issue?

scraping bots are expected to visit it, nowadays more than in previous years. a few of them are search engines, but there’s a lot of scraping for AI training, both on text and image data.

isn’t this prone to a

 || rm -rf /

or something similar at the end of the URL?

if you can docker exec, you have a lot of privileges already, so be sure to make sure this is not a danger

one more thing I remembered when re-reading the title: I think you can send messages to the VM using the qm command. it stands for qemu monitor, basically its a management tool

my solution to this is to only deal with the UPS in proxmox. it shuts down everything if the battery goes below a certain level.

I think you can configure nut to run a few scripts when something changes around the UPS. you could have a script that sends an alert through ntfy, and/or the web services that you want to use for this, but I’m not familiar with the notification system of nextcloud and truenas

would running nut-monitor in the VMs fit your use case?

only if that feature wouldn’t have a massive memory leak… can’t update even to 10.9 because it crashes the whole system the first time it tries to rescan a library.

there’s an issue, and they have a hard time figuring out the problem.

you should be able to turn it up always, to some extent. it’s in the settings on web

I have recently discovered what was causing this to me for years. It was IP specific port bindings. Ports of a few containers were only bound for the LAN IP of the system, but if DHCP couldn’t obtain an IP until the Docker service started its startup, then those containers couldn’t be started at all, and Docker in it’s wisdom won’t bother with retrying.

The reasons to move my compose stacks to separate systemd services are counting.

maybe a wireguard network is the way to go then, of course without being configured as the default destination for everything. there IPs are always fixed, but at that point you don’t even need a firewall

if I were you, I would do IP whitelisting at the firewall instead of or besides the Minecraft server