SpaceCadet2000

I settled on two.

1. Arch for my desktop, because there I like having an always up-to-date system with the latest drivers and libraries so that I can always try the latest versions of whatever it is I want to play with next. Pacman is also a pretty good package manager, and almost any piece of software that is not in the default repos can be found in the AUR. For the rest, I also like that Arch just gets out of your way and lets you configure your system how you want.

2. Debian for anything that runs unattended, like all my homelab services. It’s well tested, offers feature stability, has long-enough support, and doesn’t do weird things every other release like forcing snaps or netplan or cloud-init on you. Those “boring” qualities make it the perfect base to run something for a long time that doesn’t scream for attention all the time.

The real power of tmux, though, is that it manages the session you created.
So, one use case would be saving your current terminal setup. Instead of exiting the terminal and navigating to the project and setting up the environment again next time, you can simply detach and re-attach.

systemd: Oh yeah? Hold my beer

Technically, Lemmy could go the same way. Even though it’s an free software project, @ljdawson doesn’t own the Lemmy trademark. I think it would be prudent to call it “Sync for Lemmy”.

Also, the name change from “Reddit Sync” to “Sync for Reddit” happened long enough ago that people are probably more familiar with the new name,

Not sure if works well

You can check if something appears on https://iknowwhatyoudownload.com/

ssh tunneling can be very useful for testing or one-shot things where you quickly need access to a service that’s not directly reachable, but I wouldn’t use it as a permanent solution for anything. You quickly run into problems like:

• TLS certificates don’t work, so you get into the habit of clicking through security warnings or turning of TLS validation altogether.
• Virtual hosts don’t work
• Port conflicts when you want to access the same type of service on different remote machines, so you have to remap them and remember things like: localhost:8080 is foo:80 and localhost:8081 is bar:80
• If it’s not your infrastructure (i.e. you are an employee in a larger company), you are probably bypassing all kinds of security rules by exposing a service and your security guys will not be too happy about it if they find out.