I wonder how legal it is to change usage during a running subscription.
445 karma · joined May 21, 2020
I wonder how legal it is to change usage during a running subscription.
Glad we can still use OpenAI subscription through Pi.
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.
In what way? I've never noticed a difference.
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.
>No reasoning. No capability. Just exploitation of how the score is computed.
shudder
Guess I'll just stick with CLI only for now (via darwin-nix)
>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.
- 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.
Am I the only one feeling uneasy about this?
So... how long does it live?