ITT people trying to be edgy but I’m going to say invading Russia in the winter.

Stealing other people’s cultural heritage is their cultural heritage

Honestly the way I always look at it is just take the lifetime cost and divide it by the yearly cost and if I think the product/license deal will exist for that long (and I’ll use it for that long) it’s worth it otherwise not. Like, I have lifetime Plex and frankly I don’t expect the, to exist forever but I like the premium features and I’ve had lifetime for long enough that I’ve saved money.

Not mine but my partner’s machine (which I build and largely maintain for her) is a custom Debian install on ZFS root using ZFS boot menu and running a custom minimal i3 desktop environment.

Another option is to avoid the installer entirely and install from a live environment using chroot and whatever your distro’s installation bootstrap tool is. I started using this method to install Debian on ZFS root using this method for a while and it’s become my go-to method for installing most distros as it gives you the most control over the resulting OS. It will also often take some distro-specific knowledge but is also a valuable learning opportunity.

I tend to agree - I have no love lost for Microsoft but I’m also willing to admit when they’ve got some good tech.

Especially with ChatGPT you don’t really need to be that good at it, just good enough to read the script over and to know how to execute it.

Hey… it sorts properly alphabetically

Yeah basically all a “distribution” is is a selection of software and configurations, and they distribute (hence the name) that software and configurations as a bundle. It definitely can be daunting to learn all of this at once as a newcomer, but on the other side of that coin I’ve seen many people begin their Linux journey on a “beginner friendly” distribution who come to see that distro’s configs as default and need to unlearn/relearn many habits as they progress through their journey. I think, too, that often people who are immersed in the Linux world don’t have a great perspective on what is/isn’t confusing for a new user and often end up obfuscating things with other things that are just as complicated, if not more.

While I find that I agree with his takes like, 55% of the time, I do agree that Debian and Arch are basically the S-tier distros. So many of the other ones are basically just opinionated Debian or Arch, and while those can be useful when you’re getting started, I’ve found that for the long haul you’re better off just figuring out how to configure the base distribution with the elements of the opinionated ones that you like rather than use those distros themselves. Also, RIP CentOS. I would have put that in a high tier before the RHELmageddon (not top tier mind you, but it had a well defined use case and was great for that purpose).

It depends if you’re using them all. Systems where I have lots of applications installed (especially graphical ones) will have lots of packages, my bare-minimum container hosts will have few. I think there’s also an element of selection bias here, because people posting screenshots of neofetch on their system are also likely to be people who intentionally run very minimal systems focussed on minimizing the number of packages so they can brag about it on the internet.

TL;DR - the right number of packages to have is as many as are required for your computer to do what you need it to do, and not too many more than that.

The thing with cats is that they just kinda know themselves and offer you the deal of “yeah these are the three nice things I like to do and the three annoying things I like to do and if that jives with you, we’ll work. Otherwise, I guess just let me back outside and I’ll go back to eating birds and shit.” So every cat owner is like “yeah sure he vomits in my shoes every 2-3 days so I just turn them upside down when I take them off but he likes to sleep on the couch beside me when I watch TV and that’s our special time, you don’t really need to get it.”

So two things about this:

1. Tailscale doesn’t actually route through Tailscale’s servers, it just uses its servers to establish a direct connection between your nodes. You can use Headscale and monitor the traffic on the client and server sides to confirm this is the case. Headscale is just a FOSS implementation of that handshake server, and you point the Tailscale client there instead.

2. Doesn’t renting a $3 VPS and routing your traffic through that expose many of the same vulnerabilities regarding a 3rd party potentially having access to your VPN traffic, namely the VPS provider?

For what it’s worth, I generally think that the Headscale route is the most privacy- and data-sovereignty-preserving route, but I do think it’s worth differentiating between Tailscale and something like Nord or whatever, where the traffic is actually routed through the provider’s servers versus Tailscale where the traffic remains on your infrastructure.

This is very exciting, I’ve felt that SQLite has held back the performance of the *arrs for a long time so I’m excited to see this.

Love the app, congrats on getting out of beta! You’ve done some great work in a very short time.

I came here to say exactly this - WireGuard is great and easy to set up, but it gets harder as you add more people, especially less technical ones, as getting them to make keys and move them around etc becomes a headache. Tailscale also minimizes the role of the central server, so if your box goes down the VPN can still function. Tailscale can also do some neat stuff with DNS that’s pretty nifty.

I only have messed with it a bit, but it does require a SMTP server because it relies on sending email for account setup.

For that number of disks, I would just buy a case that holds the number of disks you want and build a computer in that case; either move your existing home lab into that case or setup a new one and export the storage over the network.

Depending on what level of malware you’re worried about, running it in a Docker container could be a solution.