I tried Tumbleweed for a while but ended up going back to Fedora. Super polished while still fast moving.

btrfs send/receive to my NAS.

Just FYI “Software” in that agreement specifically refers to Red Hat branded software, so it isn’t quite as clear cut if you debrand it before redistributing it.

I should automate something like that too. I just have one A record pointing to my IP and all my subdomains CNAME’d to that so that if it ever changes, I just have to update that one record.

My IP isn’t technically static but it hasn’t changed in the 3 years I’ve been with this ISP.

I’m okay technically with Snap, and I appreciate that it can do CLI programs as well which Flatpak can’t (to my knowledge. My issue with it is that Canonical has dug their feet in on making their store the default and only package source for everyone. It’s clear to me that they want to be the gatekeepers of software on Linux.

Yes, the only difference really is installing their custom kernel afterwards to enable missing features like touchscreen support.

It works pretty well, the only big thing still missing is camera support which will probably get solved soon.

Memmy is very new but is rapidly being developed.

We’ve come full circle

This is what I do. Btrfs snapshots and use send/receive with my NAS.

I wonder if the huge amount of API denials due to private subs had some effect on the backend.

Running my own SearX instance, fetching from multiple different sites.

Fedora on the desktop. I got my start on Red Hat Linux so I’ve stuck with it since.

For servers I use Debian. Lightweight, widely used, and gets the job done.

There’s also kbin, which seems to be compatible with lemmy.

Did you try parsing journalctl over SSH and check to see if there were any PAM or SELinux errors?

We’ve reached the end of the VC-funded golden age where they are all now demanding a return on their investment, hence why the screws are now all getting tightened.