Yeah quicksync won’t help you there.

I thought nVidia’s limit was enforced by their drivers, but that’s probably changed since it’s been a while since I looked at nvenc as a solution (quicksync, then an ARC card over here).

If you have an Intel CPU with quicksync, it will likely perform better than the 1060 in terms of visual quality, if its coffee lake or newer (8th gen).

If not, well, it’ll be fine up to whatever the stream limit is (4?).

Fair, but he said he wants to move from Windows to Linux, so I just assumed there wasn’t going to be any of those since, well, they’re not going to run in Linux anyways.

Not in a way you’re probably going to like.

You could set up a bare metal hypervisor on the system and set up a VM for your NAS, Windows, and Linux and swap between them as needed, but uh, that’s not really an exceedingly pleasant desktop use case, for a number of reasons, one of which is that you really won’t have the normal ‘sit down, and use the computer’ desktop experience.

Alternate option: run the NAS and either the Linux or Windows install in a VM, and keep it booted into, say, the desktop Linux environment with everything else being a virtualized setup.

Since android apps are required, I’d maybe go about this another way: find the app you like the most, then stand up whatever backend it uses for sync.

I was already in the FreshRSS ecosystem, but man, I don’t really like any of the android apps on offer, but swapping at this point would be annoying (bookmarks, saved stories, etc.)

good ideia to run restic as root

As a general rule, run absolutely nothing as root unless there’s absolutely no other way to do what you’re trying to do. And, frankly, there’s maybe a dozen things that must be root, at most.

One of the biggest hardening things you can do for yourself is to always, always run everything as the lowest privilege level you can to accomplish what you need.

If all your data is owned by a user, run the backup tool as that user.

If it’s owned by several non-priviliged users, then you want to make sure that the group permissions let you access it.

As a related note, this also applies to containers and software you’re running: you shouldn’t run docker containers as root unless they specifically MUST have a permission that only root has, and I personally don’t run internet facing ones as the same user as all the others: if something gets popped, then they not only do not have root permissions, but they’re also siloed into their own data in the event of a container escape.

My expectation is that, at some point, I’ll miss a CVE and get pwnt, so the goal is to reduce how much damage someone can do when that happens, rather than assume I’m going to be able to keep it from happening at all, so everything is focused on ‘once this is compromised, how can i make the compromise useless to the attacker’.

Unifi Gateway Ultra

How have you liked the gateway? Any stupid decisions that have annoyed?

My USG has decided that, after a decade, it’s going to be flaky and crash if it wants to (even after replacing it’s 4th dead PSU and 2nd USB stick) and I’m thinking it’s probably time to upgrade.

I’ll admit to both liking the Unifi ecosystem and firmly not trusting the Unifi ecosystem one damn bit, which is bit of a weird situation where I’ve been really really unwilling to upgrade anything because that hasn’t always gone uh, smoothly.

Also if you’ve never seen it, lazydocker might be something up your alley.

It’s a TUI, but it provides easy access to docker containers, logs, updating/restarting/stopping/etc them and so on.

My comment was more FDM vs resin support removal, and that it’s not like resin is all sunshine and rainbows.

If anything, modern tree supports for FDM have fixed the giant-blob-of-plastic problem with supports you’d previously get on smaller models, where you’d end up with, uh, well, a giant blob of plastic stuck to an arm or a sword or whatever.

Still not fantastic, but until someone figures out antigravity, it’s what it is.

print with supports, but removing supports from such thin, fragile bits of a model is nigh impossible without doing damage

Removing resin supports is worse, if anything.

They leave little bumps where they’re cut off that you have to then try to VERY VERY gently sand off without bending or breaking said fiddly models.

You could also use nginx if you wanted; it’ll do arbitrary tcp data with the stream plugin.

I mean, recovery from parity data is how all of this works, this just doesn’t require you to have a controller, use a specific filesystem, have matching sized drives or anything else. Recovery is mostly like any other raid option I’ve ever used.

The only drawback is that the parity data is mostly equivalent in size to the actual data you’re making parity data of, and you need to keep a couple copies of indexes since if you lose the index or the parity data, no recovery for you.

In my case, I didn’t care: I’m using the oldest drives I’ve got as the parity drives, and the newer, larger drives for the data.

If i were doing the build now and not 5 years ago, I might pick a different solution but there’s something to be said for an option that’s dead simple (looking at you, zfs) and likely to be reliable because it’s not doing anything fancy (looking at you, btrfs).

From a usage (not technical) standpoint, the most equivalent commercial/prefabbed solution would probably be something like unraid.

A tool I’ve actually found way more useful than actual raid is snapraid.

It just makes a giant parity file which can be used to validate, repair, and/or restore your data in the array without needing to rely on any hardware or filesystem magic. The validation bit being a big deal, because I can scrub all the data in the array and it’ll happily tell me if something funky has happened.

It’s been super useful on my NAS, where it’s the only thing standing between my pile of random drives and data loss.

There’s a very long list of caveats as to why this may not be the right choice for any particular use case, but for someone wanting to keep their picture and linux iso collection somewhat protected (use a 321 backup strategy, for the love of god), it’s a fairly viable option.

Yeah, I noticed that.

It’s on my to-do list for next week since I should have time to sort that out/file a bug if it’s something that’s not a configuration error.

I just uh, wrote a bash script that does it.

It dumps databases as needed, and then makes a single tarball of each service. Or a couple depending on what needs doing to ensure a full backup of the data.

Once all the services are backed up, I just push all the data to a S3 bucket, but you could use rclone or whatever instead.

It’s not some fancy cool toy kids these days love like any of the dozens of other backup options, but I’m a fan of simple and well, a couple of tarballs in a S3 bucket is about as simple as it gets since restoring doesn’t require any tools or configuration or anything: just snag the tarballs you need, unarchive them, done.

I also use a couple of tools for monitoring the progress and a separate script that can do a full restore to make sure shit works, but that’s mostly just doing what you did to make and upload the tarballs backwards.

I’m finding 8 years to be pretty realistic for when I have drive failures, and I did the math when I was buying drives and came to the same conclusion about buying used.

For example, I’m using 16tb drives, and for the Exos ones I’m using, a new drive is like $300 and the used pricing seems to be $180.

If you assume the used drive is 3 years old, and that the expected lifespan is 8 years, then the used drive is very slightly cheaper than the new one.

But the ‘very slight’ is literally just about a dollar-per-year less ($36/drive/year for used and $37.50/drive/year for new), which doesn’t really feel like it’s worth dealing with essentially unwarrantied, unknown, used and possibly abused drives.

You could of course get very lucky and get more than 8 years out of the used, or the new one could fail earlier or whatever but, statistically, they’re more or less equally likely to happen to the drives so I didn’t really bother with factoring in those scenarios.

And, frankly, at 8 years it’s time to yank the drives and replace them anyways because you’re so far down the bathtub curve it’s more like a slip n’ slide of death at that point.

Yeah I’ve been noticing that. It’s probably a case of it being cheaper for them than games, but I’ve also noticed they’ve not yet done a cycle where it’s ONLY freemium stuff, at least.

Next week, for example, is an Apex skin and a game. If it was JUST the skin I’d probably be less gruntled, but as it is, I find it hard to get too upset that I’m only getting 1 free game instead of 2.

Excessively patient. I’ve noticed there’s basically a 50/50 chance of any game I find interesting showing up for free on Epic eventually, so I mean, fine, I’ll wait a couple of years to save $60. Why pay for something that’ll eventually be given to you, paid for by some vulture capitalist’s dragon horde?

I take some of their money, get a free game: win/win.

…at this point, I’m pretty sure my Epic games library is way bigger than my Steam library, simply from the 3-5 free games a month that Epic tosses at you, of which like 1/3rd are actually pretty good.

Yeah the first run backfill was noisy, but I’m inclined to leave it there unless it gets just way too loud. If it starts making the feed just noise and junk it’ll get yanked.

It’s a bot from the programming.dev peeps: https://github.com/programming-dot-dev/rss-bot