US troop deaths in Iran conflict higher than official Pentagon figures, report says

·7 views

A Washington Post investigation has found that American military deaths during the US-Iran war are undercounted by at least four compared to official Pentagon figures. The discrepancy suggests the Department of Defense has not fully disclosed the true human cost of the conflict. The report raises questions about transparency and accountability in how the military reports casualties. Reuters cited the findings, drawing attention to the gap between official statements and on-the-ground reality.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

OpenAI Reinstates 5-Hour Usage Cap for Plus Users, Frustrating Coders Mid-Sprint

OpenAI has reinstated a five-hour rolling usage cap for Plus subscribers on its Work and Codex surfaces, reversing a removal it had made earlier in the summer. The return of the limit drew sharp criticism from users, particularly developers who had structured their workflows around the assumption of consistent access. A recurring complaint was not simply that limits exist, but that they shift unpredictably, making it impossible to plan or budget usage across a workday or week. Anthropic users reported similar frustrations, with weekly quotas resetting at irregular intervals and uncertainty over which AI models would remain accessible. The episode highlights a broader tension in AI subscription services: paying customers increasingly find that the usage they are paying for is subject to conditions that can change without reliable notice.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

FlowScript 0.1 Debuts as a Semantic Language for Modeling Apps Before Coding

Developer Erland Kjensli has publicly released FlowScript 0.1, an experimental domain-specific language designed to describe the semantic model of an application before any implementation begins. The project addresses limitations of traditional flowcharts, which struggle to capture the full complexity of modern apps including state, navigation, UI structure, and dataflow. FlowScript separates structural hierarchy, navigation graphs, and state graphs as distinct but related concepts, aiming to reduce ambiguity in application modeling. A key hypothesis behind the language is that responsive UI layouts can be treated as projections of a single underlying semantic model rather than separate application hierarchies. The initial release is available as a working draft on GitHub under version 0.1.0.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Encoding API contracts in tool schemas beats prose descriptions for smaller LLMs

A developer team discovered in May 2026 that two AI models — Opus 4.7 and Sonnet 4.6 — produced different JSON outputs from the same tool description, with the smaller model returning an incorrect structure that triggered downstream 422 errors. The root cause was not a capability difference but an exposure gap: the larger model had seen the proprietary field names during training, while the smaller one guessed plausible-sounding alternatives. Because tool descriptions are prose rather than enforced contracts, models without prior exposure to a custom schema have no validated structure to follow. The team resolved this by migrating the structural contract into the JSON schema itself, using discriminated oneOf branches with strict required fields for the nine most common pattern types. They applied a permissive fallback branch for rare pattern kinds, limiting the upfront effort to roughly one afternoon while targeting the failures that actually occurred in production.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Discovers AI Agent Was the Cause of Missing Disk Space

A developer recently shared an ironic experience where an AI agent was tasked with investigating missing disk space on their system. The investigation revealed that the agent itself was the culprit, having consumed the storage it was sent to find. The anecdote quickly gained attention in developer communities for its humorous and self-referential nature. It highlights a growing concern about the unintended resource consumption of autonomous AI agents. The incident has been dubbed a distinctly modern tech problem, reflective of how AI tooling is evolving in 2025 and beyond.

0 comments Read more at DEV Community