jstanley
If you think a toy vehicle is a vehicle then you should have answered that the toy car violated the rule.
> not everyone views a "justfied violation" as a subcategory of "violation", but rather as a subcategory of "not violation"
If it's a real tank that just happens not to work any more then it's a vehicle even if it as a monument as well.
The reason a tank in the park violates the rule is because a tank is a vehicle and the rule is "no vehicles in the park".
I think calling it a "rule" with a "violation" is bringing in some emotional baggage that some people can't see past.
If instead of "does this violate the rule?" the game simply asked "is this a vehicle in the park?" the disagreement would be resolved.
Some people seem to interpret "does this violate the rule?" as asking something more like "is this a vehicle that shouldn't be in the park?", even though the rule doesn't say anything about "should".
The disagreement is that some people think a police car is not a vehicle in the park, because its presence in the park is justified.
Rule: no vehicles in the park.
A vehicle in the park violates the rule. If it's a vehicle, and it's in the park, it violates the rule.
Anything else you're assuming should be added to this comes from your own experiences, not from the problem statement.
Otherwise it comes down to "is it a vehicle?" and "is it in the park?". There are comments from people saying they said that a police car or ambulance was not a vehicle in the park because it had a good reason to be there, which to me makes no sense at all.
The game makes very clear that it is not "would you allow this vehicle in the park?" but "is this a vehicle in the park?".
This is explicitly irrelevant, the game makes this clear.
There doesn't need to be specific narrow training data on every conceivable task.
One example would be sufficient to establish that it is "not always neutral", but I think no example can establish that data visualisation is never neutral.
I agree, but as yet we have no idea how much pain we have to pass through to get to the other side.
Which is pretty indistinguishable from people just lying about how bad it is? How are you meant to tell the difference? How can it both be true that the server is vulnerable to any script kiddie with an LLM but your exploit is too valuable to share?
And the fact that the server turned out to be not exploitable just proves that the people claiming to be able to exploit it in fact were lying.
It could be overblown if it's not true. The amount of time it took for anyone to claim the Bitcoin from the supposedly-vulnerable PHP site convinced a lot of people that the vulnerability was not as bad as claimed.
A recursive descent parser makes much more sense to me.
> It requests the lethal puzzle exactly when all three conditions hold: 28 cases, including two ads instead of three, one ad closed early, a score 1 point short, and an ad worth just under 3.5×.
> Then we ran it live, in a test copy of the iPhone app running in Apple’s simulator, and read the rule’s inputs while we played. It had three good rewarded ads on record. The score was past the line. A rewarded ad from Google AdMob was loaded and ready. The rule priced it at 72.39, against 37.41 for the last one, which is 1.94 times. It needs 3.5. So on iPhone the rule is live, reading real ad prices, and waiting for an ad worth 3.5 times your last one.
What on earth is this supposed to mean?
Existence proof: everything Claude Code does, including talking to LLMs on GPUs via the Anthropic API, and shelling out to other tools installed on your system, could in principle be compiled into one big self-contained binary (or Turing Machine if you prefer) that is able to take natural language in and produce compiled binaries out.
If you wanted to go a bit harder you could train Claude to output machine code directly, but that's not necessary. Whether the machine code comes straight out of an LLM or out of a compiler that is fed source code that comes from an LLM is a mere implementation detail, there's not any fundamental difference.