In case you aren’t being sarcastic; 2030 is the release date they gave during blizzcon.

doot doot Thank mr skeltal!

lol

lmao, even

If anyone is interested in a more thorough and recent write-up of why many of us call DHH fash, this gnome blog post is pretty good: https://blogs.gnome.org/alatiera/2025/11/06/dhh-and-omarchy-midlife-crisis/

Slay the Spire but with poker hands instead of medieval-fantasy-combat

Turns out we’re both off the mark: it’s catastrophic backtracking that is “dangerously” vulnerable to performance issues. Something as simple as (a+)+b is enough to trigger the “bad” behavior. I assume you can achieve it with back references and lookarounds as well.

This video gives a good breakdown of what exactly is going on inside a compiled regex automata that encodes such a case: https://www.youtube.com/watch?v=gITmP0IWff0

I am thankful I have been away from my arch machine this past week and so never got the chance to install infected updates from the AUR, because I for sure have gotten complacent with checking entire PACKAGEBUILDs. The checker scripts the community has put together found a single potential infected package on my machine - alvr-git - but I had last installed/updated that one on may 21 (so in theory it’s clean).

When the script is three pages long on a 4k screen, and I have ten other packages to review, I have found it’s really hard to stay committed to checking it all with my own eyes. The threat of needing to nuke my entire machine and rotates all my creds will certainly help with that, sadly.

Backreferences are bad for performance and make the grammar being matched irregular, if I remember my comp sci classes. I don’t they should be taught in a Regex 101 class.

No idea how easy this will be to follow if you’re forced to rely on text-to-speech and/or other assistive technologies, but here goes:

• to tell nginx the product is physically on /wp/, you probably want a root /wp directive
• to tell nginx the browser can point to domain.tld/post or domain.tld/english/post, you probably want two location blocks (one for each url) that each contain a rewrite directive that massages the url requested by the browser into pointing to the correct post or page location.
• for this to be in a file on it’s own, and assuming your nginx setup is pretty standard, you probably want to have the entire server block be in a file that lives in the sites-available directory and symbolically linked (“symlinked”) into the sites-enabled directory.

For the rewrites, here is the link to the relevant documentation page: https://nginx.org/en/docs/http/ngx_http_rewrite_module.html . You will need to understand the basics of how to write a Regular Expression, or get someone to write it for you. If you can’t find a human that’s available and willing to help, maybe a back-and-forth with an L.L.M. can get you to what you need (I don’t like suggesting L.L.M.s but being sighted myself I don’t really know if they’re better or worse than recommending you just work at learning how to do this on your own, given the current state of the web).

I suspect the Aquitaine region is skewed by containing both the French Basque country and the Béarn. The rest of it is pretty lacking in terms of regional identity - I would say identity is either even more local than regional or a somewhat flat, national one around here.

I’m surprised that you’re talking about models being CUDA-specific or AMD-specific. I’ve had a bunch of models running on my amd-only pc, using ollama, lemonade, and lm-studio, through either rocm or vulkan. None of these models were billed as AMD-specific. I had to do some config tweaking for ollama to use my graphics card but that’s more because I have a weird in-between-generations card that also predates the LLM hype (6700XT).

However, I did generally need to look for the GGUF format versions of things - usually accounts like unsloth have them uploaded on huggingface barely a day or two after the original version gets posted.