I’d rather people use this than reuse the same password everywhere.

Transcoding video for streaming.

Knocking is usually reads (from the header seeking), brrr is heavy writes.

HeliBoard. However for swipe typing it’ll take some practice to get used to, it’s more sensitive to swipe accuracy and you may need to reset your muscle memory.

Heroic, definitely.

You can take the windows installer from GoG and run it in a bottle, but honestly Heroic is much more convenient for that. Bottles works for any local game installer though, just like Lutris, but it has a more accessible interface, and once you’ve installed games you can add the shortcut to the bottles library which gives you a tiled view like Heroic.

If you don’t like the Lutris interface give Bottles a try.

This so much. Lists make content filtering so much easier, both foot organizing as well as for filtering.

Renders in Summit, but I turned that off because any post title starting with # is rendered as h1.

And he’s on track to become Canada’s next prime minister. I don’t like this timeline.

The other responses have so far talked about hardware setup, so I’m not going to do that. Instead I’m looking at your software setup: VMs can be comparatively power inefficient compared to containers, specially for always-on services that idle often.

Does registry still have that problem of making it practically impossible to do garbage collection on old images?

And don’t fall for the sunk cost fallacy.

Yeah, you’d have a LoadBalancer service for Traefik which gets assigned a VIP outside the cluster.

virtual IP addresses

Yeah, metallb.

The container is reproducible. Container configuration is in version control. That leaves you with the volumes mounted into the container, which you back up like any other disk.

It’s not that Seagate improved (which it may have), it’s more that WD has noticeably declined. It’s not a race to the bottom (yet), but there’s effectively no competition any more, so they aren’t incentivised to improve quality.

Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.

Use -m and limit the build job’s memory so it doesn’t kill the docker daemon.

It’s not free of risk (regional datacenter outage, account termination), but for a lot of companies the above are acceptable risks compared to the cost of managing this yourself.