This is something being sold in favor of passkeys but I can't ser how "more secure" it is for me.
I use Bitwarden, the domain name matching works exactly like passkey's. How more secure a passkey is, if it has 0 changes to this domain name detection?
Did you use SDL_VIDEODRIVER or SDL_VIDEO_DRIVER? The former one is the old parameter and the latter works. I am using it right now on a Wayland session.
There's a GitHub issue tracking this bug. It seems like SDL3 was finally released and Valve "forgot" to compile SDL3 with Wayland support.
If you're using Wayland, you can add a startup parameter to force the game to use X11 and it will work.
This issue is also affecting Dota 2.
I stopped reading when I read "Electron".
I used Heroic a few times and it's absolute garbage because it runs Electron.
They said they will offer these 2 versions side-by-side, but mark my words, a few months/years they will go with the Electron version and kill the GTK version.
why not gzip?
Haven't seen some of these before. Ones I particularly like are:
Going to therapy doesn't mean you have a disorder.
If you own a domain name you can use the DNS-01 challenge instead of hosting a web server to serve the challenge response.
With DNS-01 it will add a TXT record to your DNS zones and check if the record exists to verify that you own the domain and then issue the certificate.
Depending on which tool you use, they usually support DuckDNS and some other free DDNS providers. If you have your domain on a registrar, chances are that it's also supported.
Why is Gitness on the news and why is it being considered as the de-facto alternative to GitHub? Why is GitLab/SourceHut/Forgejo (and Codeberg)/Gitea not being considered?
Forgejo for example has almost a 1:1 compatibility with GitHub Actions and it didn't make the news. If you were to replace GitHub, Codeberg or Forgejo is a very good replacement for it.
Thanks for the suggestions!
I ended up configuring my CI pipeline to build a Caddy docker image that ships with my website files. The pipeline is also publishing the container image to the Codeberg registry and I apply the new image repo and tag to the Caddy Helm chart I found on ArtifactHub.
The only thing that's left is to setup the CI to automatically restart the pod when a new image is pushed, so it will always have the latest version.
It was easier than expected and I had a few issues like my stylesheets not being applied and image files not rendering, but it was solved by changing the pathType field on the ingress configuration to Prefix.
I don't like Cloudflare and I try to steer away from them.
Using Codeberg/GitHub/GitLab pages was an option as well, but I wanted to have it self-hosted so I have more flexibility and I get to use and customize Caddy to my liking.
Which changes, care to elaborate?