danslo

Though this program does not apply to Fable. Which is why most security researchers have started flocking to Sol.

It reads like an ad.

Secondly these are "just" IDORs, arguably the easiest class of vulnerabilities.

Thirdly it compares to GPT 5.5 and Opus 4.8.

No, we don't have Mythos at home.

from our experience, uBO Lite does not seem to be as good as the original non-Lite version

In what way? I've never noticed a difference.

It's not a freebie, it still requires a subscription and burns tokens twice as fast as Opus.

Support is slowly landing... https://www.phoronix.com/news/Lenovo-Yoga-Slim-7x-Gen11-Linu...

I could be wrong, but I believe the name is in reference to the Divine Rapier, an item in Dota 2, which is very popular among Russian speakers.

Fine. Not really different from most governments relying on private suppliers to manage their infrastructure.

DigiD itself is government-owned, but its infrastructure is managed by Solvinity (a private company). Not really different from the US gov running half its stack on AWS.

This one's pretty bad but there are some preconditions.

Requires a "rewrite" directive with a questionmark in the replacement string, and then a subsequent "set" directive that references a regex capture group (e.g. set $var $1).

Also the POC assumes ASLR is disabled.

We're enrolled in the Cyber Verification Program and Claude will happily help me look for vulnerabilities and built POCs demonstrating RCE. But when I point it to a malware sample and ask for analysis it will still refuse any work. It's incredibly frustrating.

If only the blog itself wasn't written by AI?

No reasoning. No capability. Just exploitation of how the score is computed.

shudder

The only reason I used Tailscale's menubar applet was to change exit nodes, I definitely don't need a whole UI.

Guess I'll just stick with CLI only for now (via darwin-nix)

If you're OK with it draining 3% battery per hour when you close the lid, sure.

Not sure if it's Claude Code or golsp, but I had to uninstall the plugin. Regularly makes Claude Code crash with golsp going to 100% CPU usage.

It is as long as they're not refunding you when you make a loss.

This is slop right?

This isn’t a minor gap; it’s a fundamental limitation.

His timeline? At least a decade, probably much longer.

What does that mean? Simply throwing more computing power and data at current models isn’t working anymore.

His timeline for truly useful agents? About ten years.

s/postgres/sqlite/g

I tried to switch from neovim to helix for a couple weeks, but noted down the following things that were essential to me and not implemented yet:

- Code actions on save, for example adding Go imports: https://github.com/helix-editor/helix/pull/6486

- Fuzzy search with a filepicker like telescope+rg, seems to have been added earlier this year: https://github.com/helix-editor/helix/pull/11285

- Automatically updating buffers when the files on disk change (claude, templ, sqlc, etc): https://github.com/helix-editor/helix/issues/1125

- File tree in browser, which has been rejected in favor of a plugin system which has not materialized yet: https://github.com/helix-editor/helix/pull/5768

There were a number of other things too, that I could have lived with. I guess I'll try again in a year or two.

After explicitly setting the python version to 3 in package.json? Yes please!

I appear to have crashed the server with "tic 999", sorry guys!

It doesn't matter anymore, Namecheap has taken down polyfill[.]io: https://x.com/malwrhunterteam/status/1806074377383121148

If you can understand HTML, you can understand HTMX.

I see no reason to use this if you commit often and know how to use reflog.

Now I felt even more excited. I could push fixes and refactors without having to wait for someone to code review them.

Am I the only one feeling uneasy about this?

Such proximity in mass makes the decay "difficult," resulting in a longer lifetime of the particle, and indeed Tcc+, is the longest-lived exotic hadron found to date.

So... how long does it live?