andy12_
andy12_ on Hacker News
We are 8 years into Sanchez's government. Ridiculous scapegoat.
They are very bad capitalists then, because ADIF high speed lost 200 million dollars last year.
By the way, don't act as if the Japanese high speed network is not the best on the planet. It's much more liberalized than the Spanish one.
> worth maintaining publicly via an actual government agency rather than a government-owned for-profit corporation required to compete in a market in which it is at the inherent disadvantage of public scrutiny.
The rail infrastructure is already publicly maintained via a government agency, ADIF. ADIF is not a goverment-owned for-profit corporation, its primary mandate is public service, not profit maximization, and ADIF doesn't compete with anyone, it's a state monopoly.
Just a couple of days ago the Spanish Transport minister appeared in a comedy sketch where he made fun of the current dysfunctional state of the rail system he is responsible of[1]:
> "Due to a system malfunction, the elevator will be out of service longer than usual," the public address system announces. The minister laments, "Oh, for heaven's sake. As if we didn't have enough to deal with already with Renfe."
Very funny minister...
[1] https://www.lasexta.com/programas/cara-show-marc-giro/oscar-...
But what terminology is best than "reasoning" tokens? I think it's perfect because:
- It conveys the idea that they aren't tokens normally visible or part of the final answer.
- It conveys the idea that the longer the models "reasons", the better the output.
What other term best describes both of these ideas?
Neither of those words are very specific, and everyone in the LLM space knows that "reasoning" tokens are just tokens that don't appear in the answer shown to the user.
But the thing is that across a lot of classification benchmarks, Jev is actually faster, cheaper, and
smarter than Luna (at least without reasoning). For example, look at this one from another user in this thread [1]
[1] https://hard-decisions.anth.us/models/
It's a special case for an LLM, and you can use an LLM with structure output to get similar results, but you can engineer specifically for that case to get better results per dollar for it. That's why there is little reason to adapt GPT 5.6 Sol or wathever for this task; it can already do it (at a high cost). For OpenAI to compete with Jev they have to maintain another line of models, something like "GPT-5.6-instant-decision", that is small, fast and cheap, in the scale of GPT-5 nano.
Note that I don't think OpenAI is incapable of doing it, but I just don't think they will bother with it.
I find it unlikely. OpenAI is all in training models with reasoning with RL, and Jev-like models are the total opposite. They are made to not reason at all to be fast. If you want to add reasoning on top, you might as well use a conventional LLM because you lose the price and speed benefits when you output auto-regressive tokens. I don't think OpenAI will even bother with this.
> My main assumption is that Jev is using something quite close to a conventional large language model. As evidence of this, Latent Space reports that many of the early clones are indeed LLM-based.
Not proof that this is the case with Jev though. It might use non causal text encoder for the state, which could make sense given that it's very good for its price.
I hope so. And I would really like to try an actual Jev open source model. But it will make it more difficult to market it when someone releases something like that because of so many of these "open source Jev-like model".
You can achieve open-vocabulary classification by making the final weights in the softmax come from a category encoder instead of being fixed learned weights. So instead of
softmax(encode(input)*learned_weights)
You have
softmax(encode(input)*encode(categories))
I'm not sure if Jev does it this way, but it's how you get open-vocabulary zero-shot image classification with models like CLIP [1].
[1] https://openai.com/index/clip/
All the people that are just writing an Jev-like API on top of a normal LLM are missing the point. What makes Jev special is the training data; it's how it's trained. The architecture is probably nothing special. Just a text encoder with parallel prediction branches.
I have tried many of these open-source Jev-like models on some linguistic tasks and they are so bad compared to Jev.
I think the demo is this way simply because looking at the LLM find wacky ways of implementing features without breaking the law is fun and drives the point across. In practice I imagine you would write something like "If you don't see a clear way of implementing a feature without breaking the law, ask me for directions" in AGENTS.md
If the LLM changes the laws to bypass them that's on you. The whole point of this is that you don't have to manually review most code written; only the laws. If the LLM changes the laws and you ignore it that's a you problem.
They need to be loaded into shared memory. The weights might fit in global memory if the VRAM is big enough, but they still need to be moved to shared memory for computation.
Meanwhile, my job commute is a 30 minute walk to the train station or... a 30 minute bus trip to the station (yeah, taking a bus literally saves no time at all). Plus a 50 minute train ride plus another 30 minute walk.
Honestly, I would 100% use a car for this if it weren't for the fact that doing so is literally 10 times more expensive. I'm sure this is the case for the vast majority of people that use public transport. And I just can't wait for a world of cheap electric autonomous cars where I don't need to waste my time and I can sleep comfortably on my commute.
> It sounds more like the models did close to what they were told to do
Absolutely not. If I tell a kid to "Get good grades on the next math test" I don't expect the kid to try to kidnap their teacher to extract the next questions of the exam. That is wrong, and so was what OpenAI agents did here. They shouldn't need to be told "Hey, so, don't do anything ilegal, ok?". That should always come as a given.
> not refusing bad operator prompts
I'm not saying that they should refuse a prompt! I think they should perform what is being asked! Obviously what the OpenAI agents did was against the "spirit of the task", even if it was technically according to the "letter of the task". And the agents knew this was against the spirit of the task because they knew they had to fool the task scorer.
I don't want someone to blame. I want agents to be aligned by default. Their good behavior shouldn't depend on all users at all times using them correctly, because everyone will not just[1] use them correctly at all times.
> If your solution to some problem relies on “If everyone would just...” then you do not have a solution. Everyone is not going to just. At not time in the history of the universe has everyone just, and they’re not going to start now.
[1] https://www.tumblr.com/squareallworthy/163790039847/everyone...
> This framing makes it seem like the agents all did this on their own, and the poor hapless engineers at OpenAI couldn't possibly contend with properly sandboxing them.
Great, so we can basically ignore AI alignment altogether and assume that AI models will always be, at all times, perfectly sandboxed and monitored. Surely this won't lead to any problems once someone (not looking only at OpenAI engineers) inevitably commits a mistake with future, more powerful, models.
Posted by
andy12_ on Tuesday August 25, 2026 @06:03PM
from the twitter.com dept.
> I think the fundamental principle is that this approach messes with the distribution in ways that deviate from the trained model.
But it doesn't! The distribution doesn't change at all. The only thing that changes is that sampling of that distribution becomes deterministic as per a precomputed seed.
Posted by
andy12_ on Friday July 31, 2026 @06:19AM
from the enigma.inc dept.
Posted by
andy12_ on Wednesday July 22, 2026 @06:10AM
from the twitter.com dept.
The automated AI pipeline also had an automatic grading model to try to reduce false positives.
But anyway, my point was that in that case the prompt involved was indeed pretty much "hey, ChatGPT, solve an unsolved problem, thanks."
> but it is worth noting that this wasn't a matter of "ChatGPT, solve this unsolved problem. Make no mistakes."
It wasn't the case for this, but when OpenAI disproved the Unit Distance Conjecture, it was really done autonomously by an automated AI pipeline with a completely AI-generated prompt. No human expertise required at all in the process (well, except for the final human verification).
When Google Maps routes me using a smaller secondary road instead of the main road that I would otherwise have used , I've always wondered whether that significantly changes the amount of traffic that smaller road sees. It's funny to consider that arbitrary black-box changes to the routing algorithm can have a noticeable effect to people that live there.
> Even interns can understand ambiguous asks with a bit of help
This is not a case of an ambiguous task. This is literally trying to judge a model based on information it cannot possibly know, like trying to judge someone based on whether they know what I have hidden in my backpack. In the real world an intern could look at unit tests or ask for feedback, but that is not the case in a benchmark.