But even when starting that, I was aware such patterns and remote access, yeah, this just has C&C botnet capabilities too.

It's not that deep, but there certainly is overlap with malware-esque patterns.

Especially with the hardware stuff, this is plainly put unachievable by many IT departments.

The fact that models vastly outpaced their harness and permission systems - I wouldn't dare to doubt this fact.

Claude Code on auto is still rolling a dice with its sonnet classifier - whether that IaC action I told it and explicitly stated multiple times it is permitted and authorized to run - yet it always randomly allows or denies it.

Therefore this is totally still a unsolved, perhaps unsolvable problem.

Realistically; anyone paying for llm access (anthropic, openai, gemini), is getting their access, and a service provided billed by tokens, subscription, whatever.

All the efficiency gains, which publications like deepseek v4.1 flash seriously frontload like it is their most important topic to have accomplished improvements on without diminishing performance too much - now this is a thing anthropic and anyone else also cares about, but for different reasons.

American "providers" with closed models are setting their token pricing somewhat arbitrarily, which is fine: it means more profit, and pretraining and RL experimentation is super important and expensive.

They (closed model providers) have very likely super optimized inference too, just like deepseek, but it's not at all something that any customer really has to care about - they just want the service to be as cheap and great as possible.

Sometimes it is really akin to a git clone, although it was a LLM request.

This rewarding expertise is somewhat wishful thinking.

At the end of a day, it feels and is more like gambling, even with the recommended expertise and a good approach, don't delude yourself you're simply pulling the lever too, as any novice.

FYI, I prefer discussion over being mad

The "anti LLM" or "no AI" clause is really more a "covering all ass" clause.

If you want to improve Forgejo and have that AI PR; you better clean it up of all traces - resulting in a PR that is likely neat and going to be merged.

I see no issue with that. It simply enforces a pace and process that is very befitting and in my opinion mandatory for such a central system they're maintaining.

1. "Grokking" was shown on 4-digit modular arithmetic with a 1-layer transformer; this article extrapolates it to AGI and a $10B training run with exactly zero intermediate evidence.

2. The "small dataset" is 25 trillion tokens - literally the size of current frontier training sets - but calling it small sounds revolutionary.

3. BabyLM has spent 4 years failing to produce grokking on constrained data; the paper gets a footnote saying "those models were too small," which is unfalsifiable until someone burns $10B.

4. Chain-of-thought is already empirically required for frontier performance - it's expensive, bizarre, and nobody predicted it - yet somehow we're supposed to bet the farm on a phenomenon that has never scaled past arithmetic. We need that data, even if it is just "Actually, ..."

5. If you want to chase "recurrent depth", loop transformers rumored in Mythos/Fable are at least grounded in actual engineering; grokking-at-scale is just vibes ai bro science.

More data is and will always be the answer. Why are all labs distilling from each other?

As if it really would work like that. The noise added by the verbosity alone is not taken care of enough, and this entire thing belongs on the great pile of ai vaporware.

The simple fact that people will act on it and believe just because what they insinuated as a prompt and the answer being churned out on the screen looking somewhat readable.

That alone was going to seed so much discord and reinforce invalid messages, truly "oh shit".

With this, I am sticking to deepseek-v4-pro entirely.

It killed my daily csharp vscode driver couple of years ago, only now catching back up somewhat, but still unusable for bigger solutions.

That move made me gravitate towards vscodium, and avoiding csharp where possible.

Microsoft's move only recently got more understandable to me, because Cursor and others basically stole vscode to establish their "empire".