If you’d rather keep Vikunja as the backend and web UI, it has a CalDAV endpoint, so you can point DAVx5 at it and use Tasks.org or jtx Board on Android for the reminders themselves. That gets you native Android notifications without email, and you keep the web interface for planning. Vikunja’s CalDAV side is less mature than its web UI, though, so test whether due dates and reminders come across the way you expect before moving everything over.

For notifications that aren’t tied to a task app (say, “remind me when X happens” from a script or Home Assistant), ntfy is the simplest self-hosted push to Android, as mentioned above.

Nice find. One thing to check before buying parts: the README says it works with line-level sources through a USB audio adapter. Most turntables output phono level, so unless yours has a built-in preamp (look for a PHONO/LINE switch on the back), you’ll need a phono preamp between the deck and the USB adapter. Without it the signal is very quiet and has no RIAA equalisation, so it sounds thin.

Also, AirPlay buffers for a couple of seconds, which is fine for listening, but you’ll notice the delay if you’re standing next to the speakers while dropping the needle. The automatic start/stop on signal detection is the clever part for a turntable.

Two things specific to the RX 6400 worth knowing:

• It’s a PCIe 4.0 x4 card. On a PCIe 3.0 board the link is half as fast, and that hurts most exactly when a game spills past the 4 GB and starts moving textures over the bus. So on a 3.0 board, keeping texture quality low enough to stay inside VRAM matters even more than usual. MangoHud can show VRAM use live, so you can see when you hit the ceiling.
• For emulation, VRAM mostly goes on internal resolution and texture packs. In Dolphin, PCSX2 and the like, 2x-3x internal res is usually comfortable on 4 GB; 4x+ with high-res texture packs is where you’d start running out.

It also has no hardware video encoder, so don’t count on it for recording or streaming, but for older games and emulation it’s a perfectly decent card.

The most useful number you can get is from your own stack: put your actual app on the box and hit it with k6 or wrk using a realistic mix of pages, and watch memory rather than CPU. On 2 GB the failure mode is almost always RAM: too many PHP-FPM/worker processes plus a database on default buffers, then swap thrashing and the OOM killer, long before the single core is the limit.

What buys the most headroom on boxes this size:

• cap the worker count (pm.max_children or the equivalent) to what actually fits in RAM
• size the DB buffer pool deliberately instead of leaving defaults
• zram for bursts
• serve anything static or cacheable straight from nginx so it never touches the app

And rate-limit or block the obvious scrapers. As someone said above, bot traffic is often the real load.

If you end up running it headless (game streaming host, Jellyfin/Immich worker, whatever), two small things save a lot of hassle:

• Get an HDMI dummy plug (a “display emulator”, a few euros). With no internal panel detected and nothing on HDMI, the GPU often has no proper display to render to, and Sunshine/Steam streaming in particular wants a “real” display to capture at the resolution you pick.
• Check the BIOS for a “power on after AC loss” / “auto power on” option. Plenty of laptops don’t have it, but if yours does, it comes back on its own after an outage like a proper server. Otherwise Wake-on-LAN from one of your mini PCs is the fallback.

And since storage is your bottleneck right now, open it up and see if there’s a second M.2 slot. Some of these chassis have one, and then it could hold some data while also taking the Immich/Paperless ML jobs on the 3050Ti.

For anyone testing the beta, the two lower-level changes are probably the ones most worth poking at before the 15 October release, since they’re the ones most likely to break things silently rather than visibly:

• Rust coreutils is now complete, including cp, mv and rm. If you have backup scripts, deploy scripts or anything that parses the output of these tools or relies on less common GNU flags, run them on the beta now and report differences upstream to uutils. Behaviour differences in edge cases (symlinks, sparse files, odd permissions, error messages) are exactly what a beta is for.
• dbus-broker replacing dbus-daemon: mostly invisible, but if you have custom D-Bus policy files or services that do unusual things on the session bus, it’s worth checking the journal for warnings after login.

The OOM change (core desktop processes getting lower OOM scores) sounds like a genuine quality-of-life fix for anyone who’s had the whole session killed while a browser ate all the RAM.

Adding to the Workers theory: if it is a Worker, Cloudflare adds a CF-Worker request header to every subrequest a Worker makes, and its value is the zone the Worker belongs to (e.g. something.workers.dev or the owner’s own domain). It’s not something the script can strip, so if you add that header to your reverse proxy’s log format you should be able to see exactly whose Worker is probing you.

That gives you two practical options: report it through Cloudflare’s abuse form with the zone name (they do act on Workers being used for scanning), and/or drop any request that carries a CF-Worker header at the proxy, since nothing legitimate should be hitting a DNS-only Lemmy host through a Worker anyway. Federation traffic from other instances won’t have it.

Nice, this is one of those automations that pays for itself the first winter. Two small things that might make it nicer to live with:

The loop with the namespace can be a one-liner, and you can limit it to the next couple of days so a cold snap six days out doesn’t nag you every morning all week:

{{ (daily['weather.forecast_home'].forecast[:2]
    | map(attribute='templow') | min) < minTemp }}

And to stop repeat alerts once you’ve actually done the work, pair it with an input_boolean like outdoor_water_winterized: add it as a condition (only notify when off), send the notification with an actionable button (“Done”) from the companion app, and have the button event flip the boolean on. Then a second automation turns it back off when the forecast lows climb above, say, 8 °C for a few days in spring. That also covers curbstickle’s point if you ever add more taps, one boolean per tap.

I do, but with a few tweaks that cut most of the junk the other comments mention:

• Point Contact: at a dedicated alias, not your main inbox, and filter it hard. If the noise gets bad you can drop the alias without touching anything else.
• Add a Policy: line linking to a short page that says plainly there is no bug bounty and no payment for reports. Most beg-bounty mails are mass-sent with a payment ask, so this gives you something to point them at and lets you bin them without guilt.
• Don’t forget Expires:, it’s actually required by RFC 9116 and a lot of hand-written files leave it out. Set a calendar reminder to bump it.
• Serve it at /.well-known/security.txt; the root path is only a legacy fallback.

Whether it’s worth it for a homelab is debatable, but if you host anything other people rely on (a Matrix/Lemmy instance, a shared Nextcloud), having one real contact path beats someone finding a hole and having nowhere to send it.