All video codecs are lossy, meaning you will lose some quality. AV1 and H.265 are modern video codecs with the best quality to bitrate ratios, meaning you can get better quality for the same bitrate, or the same quality with a lower bitrate. The downside the these codecs is that they are very complex and computational expensive to do in software. You’ll want to make sure your GPU supports hardware encoding for the codecs you intend to record with. The reason most people will recommend AV1 over H.265 is that AV1 is royalty free. With H.265, companies have to pay a royalty to use H.265. Because of this, most companies (Netflix, YouTube, Facebook, Twitch, etc.) want to use AV1 going forward, meaning in the near future, it will probably be the dominant codec.

It’s been a while since I took statistics, but yes, I guess that is a binomial distribution. It does not influence the results in the way you are implying it does, though. The calculator does actually account for it (the Population Proportion input), and the sample size actually decreases the lower/higher your proportion is. My point was that a question like, “Do you watch anime weekly,” is not like a question like, “How many hours of anime do you watch in a week,” where you certainly couldn’t assume a normal distribution for the number of hours watched.

Normal distribution with regards to what? “Do you watch anime weekly” is a binary question. There really isn’t a distribution associated with that.

You don’t need a massive sample size for surveys to give meaningful information. Play around with this sample size calculator if you want to see what the margins of error are: https://www.calculator.net/sample-size-calculator.html?type=2&cl2=95&ss2=4000&pc2=5&ps2=500000000&x=Calculate

The Trine series is pretty fun. It’s a 2.5d puzzle platformer game. There are some combat bits, but most of the game is puzzles. I’d recommend the second one.

the timer has no idea if it was triggered during last boot. It only has the context of “this” boot, so it will do it right after a reboot and set a timer to start the service again after a week of uptime.

This is not correct. Persistent=true saves the last time the timer was run on disk. From the systemd.timer man page:

Takes a boolean argument. If true, the time when the service unit was last triggered is stored on disk. When the timer is activated, the service unit is triggered immediately if it would have been triggered at least once during the time when the timer was inactive.

OP needs to remove Requires=backup.service from the [Unit] section so it stops running it when it start the timer on boot.

You have the timer requiring backup.service, so it will run that service every time the timer starts on boot. Remove Requires=backup.service, and that will fix the issue.

Well, for one, it’s network attached storage. If it’s not present in the network for one reason or another, guess what, your OS doesn’t boot… or it errors during boot, depending on how the kernel was compiled and what switches your bootloader sends to the kernel during boot.

Just use nofail in the fstab.

Second, this is an easy way for malware to spread, especially if it’s set to run after user logon.

If your fileshare is accessible to you, it is also accessible to malware running as your user. Mounting the share via a filemanager doesn’t change this.