leobuskin

There’s no way the current safeguards affected by “trust” score in dynamic way (and the score is fluctuating), more like the tiers of trust are being proxied through different policies - it’s a separate story. But I observe the same “cyber” issues working with Linux kernel and drivers as people who went through CVP/T1 (which is wild, to be honest). Hypervisor interactions trigger immediate “cyber” response, it’s impossible to work with Opus 5.5 doing anything low-level with custom or third-party devices. Only 4.8 can assist, and it’s a huge difference in code quality and approaches.

Anthropic had/has a great opportunity to equalize the landscape, but they are choosing the Cyberpunk 2077 branch for some reason.

US/EU here (both, due to traveling), same story with anything related to modifying existing weights or SotA approaches in training/research, it's not a geolocation issue. The safeguards don't check your IP (but pretty soon will check someone's IP [pun intended])

It is required. The first week of release I told here how GLM 5.3 was happy to redteam, it’s not anymore. Models modification, offensive cyber, exploits - requires significantly bigger prompt/scenario engineering, and still hits refusals.

And those services are oversold and underdone. 30 tk/s on Refuseless, huge TTFT, looks like a damaged quant (it’s NVFP4 and you see wild random stuff periodically, including foreign languages). Most of them using third-party quants (dealignai?)

If someone here wants to rent 8x B300 together to avoid problems all those services have - ping me via email. I don’t want to sell, I want to work.

X is under Cloudflare (and according to some of my probes may even use some parts of CF stack)

do you know what kind of mixers people use nowadays for such transfers?

Why would you prefer WSL over native Linux? What's the rationale here?

That's totally fine, I'm pretty sure people continue to use JB by inertia, requirements, personal preferences, lack of alternatives, inability to introduce some, or whatever is the reason behind. It's all for good. Most (I'd even say all) people I know jumped off paid JB products within the last two years (C#, Rust, Python, Web stacks), even being evangelists previously (I was religiously protecting and advertising JB in all possible holywars). And in 2023 we already were betting if there's a place for JB "as-is" in the current/future landscape. Too slow, too enterprisish.

CC + my own custom tools, I don't see any reason to pay for devtools in 2026 (same as trying to monetize them, or even just share/distribute). My first custom solution was built on top of JB's core in early 2024, btw, but not any more. JetBrains "suite" doesn't really lock you in, it's more like "aura" of the product itself that made me attached for almost 13 years (I never was able to switch, I still think VS Code is so ugly and counter-intuitive in comparison with JB).

It's purely management fault, it happened around 2022-2023. They had all the chances to become a great agentic IDE/harness at some point, if they would start in time, support plugin developers, allocate a proper team instead of 2 people and some semi-random internships. A lot of users were questioning this publicly and privately with them, we all knew how it will end this way. JetBrains lost, no one wants their Junie in 2026 (and didn't want in 2024-2025, whatever was the name of the integration at that time, it was awful). I was on Ultimate Plan since 2012, appx. I quit entirely in 2024. They asked to answer a few surveys over the last few years - even the questions there were far from reality. RIP, JetBrains, it's mostly unrecoverable at this point.

It’s two different dimensions in this case. VCS doesn’t preserve your local history (in JetBrains’ terms) of changes (and it wasn’t meant to by design)

Astra had an explicit medium/xhigh levels, Fable - just Fable. What reasoning level was used? Why not multiple were tested?

I’ve scrolled the article, but haven’t noticed any remarks about Fable’s levels.

An example with manual combinatorial exclusion in “not_for” field made me cry, this is a wild hybrid of code logic, textual definitions, and AI blackbox. It’s a cool idea, but the “glue” layer is too boilerplate-ish

mmm, someone decided to reuse `zookeeper` name, seriously?

Heretic?

That’s the first model that fits CC as it’s own, zero issues, but probably ZCode or whatever z.ai’s cli is.