> VARA’s developer released a new version 4.9.1 which had a logic bomb that completely breaks compatibility with all prior versions starting on 1 Jan 2027.
Is there more coverage? That sounds downright evil.
I participated in some discussion on a private discord where the claim was made that the developer did this. I reversed the binary with an LLM and confirmed it myself. I’m aware of at least one ham radio YouTuber who has posted a video about this.
I presume it will get more coverage as more people learn about the new release and the compatibility break.
> WireGuard by itself is not a stealth VPN, but the things that make a VPN "stealthy" are all things you'd layer on top of a WireGuard design, not thread through the middle of it. A datagram-based protocol can run under any obscured transport.
Yes, two ways failing to combine tool calls is a real deficiency for the LLM's user: it costs money and can get you rate limited.
Every turn forces you to pay $ for cached inputs and possibly gets you rate limited on TPM.
At 500k context and $0.26/M-tok cache read price, every time it combines two tool calls instead of taking separate turns would save you $0.13. That could add up.
Maybe the provider sets a rate limit of 2 million TPM. That's just 4 turns in 1 minute before you start getting 429s. Cutting them in half by combining calls can save that.
All else equal, we definitely want models combining tool calls!
It also makes models completely ungovernable and unfollowable.
Asking for user permission before an action is pointless. it's not going to use a single `write`, it's going to run a 25 line perl script without even newlines.
At this point just completely remove permissions, and leave only one tool, a rust-like scripting language.
But this also drives usage up, because you rely less on yourself, and more on the increasingly black-box that is the subagent-of-subagent that you are not even going to check the result of.
It depends on what you actually want to ask permissions for. We're still doing trivial script execution, but we could go further. Capabilities like "do you allow giving access to JIRA read only token" would be a massive improvement. But there are other paths too.
Polymarket does. In the US they are a registered CFTC exchange for trading event contracts. That gives them some degree of protection from state actors. It also increases the odds that if you make money you'll actually be able to withdraw it unlike many of these markets. They also operate in actual dollars not make up crypto tokens.
Note that Polymarket's non-US business is crypto blockchain whatever so ... good luck with that. The ability to get your money out could disappear at any time and as far as I know there's no recourse if they just decide to screw you over. Not that CFTC is super effective but it is something.
> In the US they are a registered CFTC exchange for trading event contracts. That gives them some degree of protection from state actors
So is Kalshi. The entire question is how the CFTC made up the authority to regulate gambling out of statute that only ever mentions exempted commodities.
Or for historical context, this is all Twitter's fault since its character limit included links too.
reply