xinayder

That doesn't seem to be the case. From what I read on HN, the dev quit because he thought it didn't make sense to submit CVEs for temporary/wip solutions, and F5 thought otherwise.

So as I see it, the developer quit because he didn't agree that a CVE should be opened for a work-in-progress solution that was live on Nginx.

So... not using Signal because it's based off a conspiracy theory that it's secretly funded by CIA?

Well, let's stop using RSA and encryption because the most used secure crypto algorithms today were created by none other than the NSA!

EDIT: None of the alternatives provided are good alternatives for Signal. Matrix is an extremely complicated protocol that lacks some features compared to normal IM apps (I use Matrix and the experience is quite close to a standard messaging app). XMPP is dead and has a very niche userbase. The others are not suitable for being a daily messaging app.

Signal is a good alternative and while I do agree with some points, they are not bad enough to prevent you from using it (e.g. not having usernames).

It's still not an excuse to just ignore the security update because you might not be a target for hackers.

Just check your logs, there's probably a dozen or more requests trying to access wordpress pages on your server, or login via SSH. They want to take over your server so it can be part of a botnet.

I think so, but if you check the official image you can definitely find out how to include custom plugins in it. I think the documentation might mention a thing or two about it too.

You can install the log transformer plugin for Caddy and have it produce a readable log format for fail2ban: https://github.com/caddyserver/transform-encoder

I had this setup on my VPS before I moved to a k3s setup. I will take a look at how to migrate my fail2ban setup to the new server.

I tried changing the graphics settings on my mid-range PC and they barely make any difference. You can tune FSR to the max but I don't think there will be much notable difference in performance.

The only thing I see they did wrong was to disclose the vulnerability before waiting for a comment from the software company.

My only issue with the latest update is that the app doesn't start minimized by default. Otherwise, I really like the program!

I had a similar issue with my laptop, where Arch wouldn't be recognized as a bootable system on my NVMe drive unless I disabled RST with Optane on the BIOS, setting it to AHCI mode.

I do remember seeing a similar issue a while ago as well, but I don't remember if the user managed to fix it.

I could suggest removing the Windows drive, installing Arch and checking if everything works, then plugging the Windows drive back in. Windows loves to delete non-Windoes bootloaders from every drive it can.