Maybe not a service in the typical sense, but setting up your router+server to route your home network traffic through a VPN is a fun project.

My router (MikroTik) supports WireGuard, so I can use it with Mullvad for the whole house—but wg is demanding and it’s a slow router, so while it can NAT at ~1Gbps, it can’t do WireGuard at more than ~90Mbps. So, I set up WireGuard/Mullvad on a little SBC with a fast processor, and have my router use that instead. Using policy based routing and/or mangling, I can have different VLANs/subnets/individual hosts selectively routed through the VPN.

It’s a fun exercise, not sure I implemented it in a smart way, but it works :)

I assume you’re referring to the cuckpdate chair.

Whenever I have a Linux box without Internet I just USB tether an Android phone—if the phone is on WiFi then it uses that (not cell), so it’s basically just a WiFi adapter that’s almost universally supported. (I think it NATs, so in some circumstances won’t work, but good enough for most emergency use cases.)

I used Photoprism years ago, so my knowledge is probably pretty outdated.

My experience of Photoprism was that mobile was not tightly integrated. At the time I used Syncthing to sync photos — it worked ok for me, but I wasn’t going to set it up on my partner’s phone, for example.

Immich Just Works on both mobile and desktop. Multi user is great, sharing is great, and the local ML and face detection work remarkably well.

Whatever works for you is the best of course! Immich fits the bill for me, and it was very much worth it for me to “buy” it.

Regarding DNS servers, what router do you have? Some routers have simple enough DNS capabilities — I have a MikroTik, and have it set up with DNS entries for internal services (including wildcard). Publicly accessible services just use my registrar’s DNS (namecheap — no complaints).

Matter is also local—provisioning can be a PITA but once done I’ve been pretty happy with even the cheap Matter WiFi smart bulbs. Home Assistant supports them very well.

Cheap bulbs can be a little buggy, which usually means I need to power cycle some of them now and then.

My lights and motion sensors were obviously unaffected (HomeAssistant). My Emporia Vue2 power monitor would possibly have stopped working, except I flashed it with ESPHome firmware, so it’s local only, and of course it was fine. My security cameras (Frigate) were also fine.

If my smart home devices are going to stop working, it will almost certainly be my fault, thank you very much!

You’re right, for new drives it looks like a little more with this 20GB retailing for $230, or $11.50/TB.

For refurbished, I recently got a factory renewed 12TB Seagate for $112 ($9.33/TB), but that price is now up to $199 for the same drive (!).

Official numbers here https://www.debian.org/mirror/size

About 4.4TB, but that’s all architectures and (I believe?) all distributions (stable, testing…).

If you only want source+all+amd64+arm64, and only want stable, it will be smaller of course.

Not nothing, but at $10/TB or so, it’s not much.

And if you’re following 3-2-1, I’m pretty sure the “1” is already handled for you :)

On low end CPUs you can max out the CPU before maxing out network—if you want to get fancy, you can use rsync over an unencrypted remote shell like rsh, but I would only do this if the computers were directly connected to each other by one Ethernet cable.

If you’re running it via docker compose it’s trivial to upgrade, and there are no breaking changes. Pull, down, up, you’re done.

Frigate is pretty good, too. I’ve only been running it for a few months but I’m very happy with it.

Though, technically that leaves you more at risk of ransomeware or something that overwrites your data.

I rsync as well, but use snapshotting on the remote drives. So, a bad rsync would suck but shouldn’t really result in data loss. Ransomware on my local+remote server would of course be very bad…

I do something similar — I have a raspberry pi and a HD, with daily rsync and snapshots (monthly retained indefinitely, weekly retained for a month, daily retained for a week). It’s at family’s house, connected to my home via WireGuard via a VPS. Tailscale (or anything really) would also work here.

It’s a great setup! Just have some watchdog reboot if it can’t talk to home (a simple cronjob with ping -c1 home.lan || reboot or similar).

Even our “slow” 35Mbps upload speed is way more than enough for incremental rsyncs of my Immich library. The initial sync was done in person, though.

I got one from goHardDrive on eBay (link). It was cheap enough, looks flawless, and knock on wood has been working fine.

Googling around, the brand gets…mixed reviews. My use case is such that of this drive fails it’s not a big deal.

I’ve honestly never understood people who feel the need to “replace” Spotify. … Spotify has never made sense for my use-case.

I don’t know how to say this, but…you have extremely uncommon use-cases:

…during those times, my phone is either fully turned off (so I’ll use an MP3 player), or it’s in Airplane Mode.

Many people listen to music on stereos and don’t necessarily want a device plugged in, so

I just download the music I like to my device and listen to it via VLC.

either doesn’t work or is substantially less convenient than e.g. casting from a phone.

Not hating on your setup at all, but it’s very niche, in my experience.

Some would call the former command cat abuse.

In short, unless you want the contents of a file printed to stdout (or multiple files concatenated), the command can probably be written without cat, instead using the filename as an argument (grep pattern file) or IO redirection (cmd < file).

Stylistics and readability are another thing though.

Yabai+sketchybar make tiling+virtual desktops…at least usable on mac.

Of course, I’d take i3 any day of the week.

Coming from Debian, it was…not expected. I understand how and why it happened, but the user experience was surprising.

Debian keeps the previous kernel around, which makes perfect sense to me — in the event that a kernel update borks your system you can just load the previous one. This would probably only happen due to out of tree modules (looking at you, Nvidia…).

Coming from Debian, it was…not expected. I understand how and why it happened, but the user experience was surprising.

Debian keeps the previous kernel around, which makes perfect sense to me — in the event that a kernel update borks your system you can just load the previous one. This would probably only happen due to out of tree modules (looking at you, Nvidia…).