https://en.wikipedia.org/wiki/Reproducible_builds
e.g. https://f-droid.org/docs/Reproducible_Builds/ for F-droid's efforts on it. Debian, Arch Linux, and other popular linux distros also have their own efforts ongoing
https://en.wikipedia.org/wiki/Reproducible_builds
e.g. https://f-droid.org/docs/Reproducible_Builds/ for F-droid's efforts on it. Debian, Arch Linux, and other popular linux distros also have their own efforts ongoing
I'm guessing they didn't go with .fur because it's already been used before by FurNIC (per wikipedia)? .furry is sort of unwieldy to pair with most website names that aren't specifically designed to go with it, so it's a bit stifling in that sense (like, lemmy.fur vs lemmy.furry)
Tv show seasons/episodes can be subscribed individually, and you can change behavior e.g. 'stop after this season'.
You can set up quality preferences per show and even more complicated choosing with a lot of regex, and it actually works very well. If you do it this way and enable upgrading, the media will also automatically get its quality upgraded when something "better" comes out.
"TRaSH guides" has a lot of regex that can be copied from, and I also have a ton of my own preferences codified.
The core arr stack (radar, sonarr, optionally seerr) is generally just a really smooth way to handle everything at the cost of an initial learning curve. Maybe overkill for some people, but I think it's a straight upgrade if you set it up right
One of the biggest advantages to me is that my friends and family can go into Seerr and click "I want this show" and it will magically appear in a few minutes without my intervention. Also, for TV shows specifically sonarr will automatically get new episodes for series that you're subscribed to
I think generally people use imdl in scripts nowadays, but I don't know if there's any GUIs or anything.