My recollection is that Fail2Ban has some default settings, but is mostly reactionary in terms of blacklisting things that it observes trying to get in. Crowdsec behaves in a similar vein but, as the name implies, includes a lot of crowdsourced rules and preventative measures.

Now that you have a working setup, make a backup. Then, experiment with either starting over and only doing a few of the steps OR experiment with removing some of those parameters. Find your minimum set of working parameters this way, then you can look them up to find out more about what each parameter does that you discovered to be essential.

I can for sure tell you that passing the render device is required for hardware transcoding, but I’m not sure what else is required. The iommu and vfio parameters are related to passing the entire gpu device into a container, but I don’t know anything about Proxmox so I can’t comment on whether that would be required for your situation.

Same here! 10gb free is more than enough for the volumes I mount on my containers with config, etc

Does it skip the recode completely if the format is already opus?

I really wish the WSL extension wasn’t locked behind VS Code. My workflow is heavily reliant on it which locks me into the proprietary IDE.

Maybe apps will finally feel free to bundle LAME instead of forcing you to download it externally!

Permanent zero-cost activation that survives reinstalls

KMS requires phoning back to MS periodically to keep the license activated. It’s still “permanent” because there’s no limit on duration (as of now at least).

HWID activation registers a hardware ID in MS servers to permanently license it. That means no renewal, just forever activation that survives reinstalls.

100% in the same boat. WSL and VSCode is basically a requirement for me, and codium can’t do the WSL linking.

Just want to shout out to reviewbrah for giving us this absolute gem of a phrase

Fix is to address a critical CVE:

Specific handling of an attacker-controlled VP8 media stream could lead to a heap buffer overflow in the content process. We are aware of this issue being exploited in other products in the wild.

Unfortunately, I think you’re unlikely to find anything besides the ones made by the big companies: Google, Apple, Samsung, and Garmin are the ones I know. They each have agreements with the banks and credit card companies to handle the secure exchange of data required for the touch payment system. In fact, there are still some issues resulting from a lack of cooperation (such as Citi Bank not working with Garmin Pay because they can’t be bothered to set up the relationship). I imagine an open source software would be unable to get the banks to pay attention to them to establish a partnership, or would otherwise be declined because the financial institutions wouldn’t trust them.

You maybe know this but GitAhead was discontinued, and the maintained fork is called Gittyup: https://github.com/Murmele/Gittyup

Open source is a definite plus, but tbh not a requirement for me. Actively maintained, free, Windows and Linux, and simple. Oh, and it has to have a dark theme 😄

Fork is only “free” in that the evaluation period is indefinite. This is generous and clicking through the nag isn’t a huge deal, but I develop on both Linux and Windows and I need a client that supports both.

Unfortunately, GitLens is by GitKraken. Seems like they might not restrict it for private repos, though, I’ll check it out.

Bookmarking this. I have such high hopes for this! I recently went searching for my new git GUI, looking for something free, cross-platform, and simple. Basically what I found is the only one I like is GitKraken, which is not free (I have private projects, which GitKraken paywalls).

If this ends up anything like how these screenshots look, this will be my new client! Do you have a Patreon or other donation mechanism?

That workaround has been implemented for mobile clients too https://github.com/immich-app/immich/pull/2101

Great JoCat reference 🤣