Personally I still use Hexchat since it is still supported by my distribution for several years. It won't receive new features but security fixes only which I'm fine with.
If Hexchat is in Trixie repository (which seem to be the case) it will be maintained across its lifecycle which will be a couple of years. If you're fine with receiving security patches only, then there is no need to swap the client.
As for myself I'll stick to Hexchat as well for the time being since it just works.
I think it was about 28h when my first child way born.
Usual day, up at 6am, normal day. Then wife stated around 10pm 'alright, we need to go to the hospital'. Few hours later at around 6am child was born. The aftermath and heading home took a few hours as well and finally got some rest at 10am.
The funny thing is I did not sleep that much then. I think about 4 hours and was good to go.
Oh yeah, and my wife was probably also happy to get some rest lol.
Not banned. I deleted all my posts and then quit Reddit the moment they tried to ruin (and were mostly successful it seems) 3rd party apps with changes to their API. Screw them.
Indeed. Immich is the way to go. While stating heavy development I find it quite stable. Did not have major issues with it.
However I don't use their interface much. I just use it as 2nd backup location to automatically upload stuff from my phone to something else than the big G.
Obviously this need some sort of server but a VPS will do.
Use a firewall to block all outgoing packages through all interfaces but lo and tun (or wg for Wireguard). Like this for iptables:
bash
-A FORWARD -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -d 1.2.3.4/32 -p udp -j ACCEPT #replace with public IP of your VPN you try to connect
-A OUTPUT -p icmp -j ACCEPT
-A OUTPUT -o tun+ -j ACCEPT #replace with wg+ for Wireguard
-A OUTPUT -j REJECT --reject-with icmp-port-unreachable
If you are paranoid you could mess with INPUT table as well but if OUTPUT is configured properly nobody well ever know your real IP address.
Not sure how well this works with Docker and such, I use LXC containers.
The funny thing is that I am actually seeding Linux ISOs (yes, real ones). The reason I am using a VPN to seed those is because the ISP is complaining about random peers hitting (non-existing obviously) addresses in private IPv4 ranges (like 172.16.1.1) and instead if simply dropping those packages at the switch ... oh well. I guess some people have multiple peers connected to each other via private networks but external peers don't know about these connections and simply try to reach them on their private addresses over public internet.
Anyway yeah I could mess with routing table on my server and null-route those ranges but I have an active VPN contract already so why not using it?
Personally I still use Hexchat since it is still supported by my distribution for several years. It won't receive new features but security fixes only which I'm fine with.