White House Defends Media Ban, Calls Press Access a Privilege

·1 views

The White House has filed a court document defending its decision to ban certain media outlets from official access. The administration argued in the filing that press access to the White House is a privilege, not a guaranteed right. The ban reportedly affects outlets including CNN, Politico, and MS Now. The filing represents the administration's formal legal position as the matter is being contested in court.

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)

TypeSafe's Jev Matches Mid-Tier LLMs but Trails Frontier Models After Eight Days

TypeSafe AI launched Jev on September 15, 2026, a hosted 'System One' model designed to answer typed classification and scoring questions about text rather than generate free-form responses. Independent testing conducted over eight days found Jev performing on par with mid-priced large language models while lagging 6.5 to 11.5 percentage points behind frontier models on the most reliable benchmarks. The model showed the best out-of-the-box probability calibration among tested models on familiar English tasks, with most calibration errors correctable via a single temperature adjustment. TypeSafe, co-founded by Diogo Almeida, Sasha Sheng, and Erik Gafni, raised a $40 million seed round led by DCVC, and prices Jev at $0.042 per million input tokens with free output. The review drew on 14 arXiv preprints, 104 GitHub repositories, and 33 blog posts, noting that the majority of positive coverage either restated vendor claims or came from launch partners with a commercial interest.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Gemma 4 26B Trails Jev by 2.1 Points as a Decision Model on Single AWS L4 GPU

A pre-registered benchmark tested Google's open-source Gemma 4 26B model as a decision classifier on a single AWS EC2 L4 GPU, comparing it against TypeSafe's hosted Jev 1.13.0 service and Google's DiffusionGemma variant. Evaluated on Bespoke Labs' 3,880-record public test suite, plain Gemma 4 26B scored 2.1 percentage points below Jev overall, with no meaningful gap on yes/no questions but a 4.5-point deficit on multiple-choice items. Jev showed better out-of-the-box calibration, though fitting a single temperature parameter on just 50 labels brought Gemma's median calibration error to within 0.01 of Jev's. Compared to DiffusionGemma, the plain Gemma read matched accuracy, performed similarly after calibration fitting, and ran 1.9 to 5.1 times faster per decision. All per-item outputs and pre-registration documents were committed to a public GitHub repository before any model calls were made.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Gemma 4 26B Trails Jev by 2.1 Points Overall in Benchmarked Decision Model Test

A pre-registered benchmark tested Google's open Gemma 4 26B model as a decision model on a single AWS EC2 L4 GPU, comparing it against TypeSafe's hosted Jev 1.13.0 service and Google's DiffusionGemma variant. On Bespoke Labs' 3,880-record public evaluation suite, plain Gemma 4 26B scored 2.1 points below Jev overall, performed comparably on yes/no questions, but lagged 4.5 points behind on multiple-choice tasks. Jev showed better out-of-the-box calibration, though a single temperature adjustment brought Gemma's median calibration error to within 0.01 of Jev's. Against DiffusionGemma, the plain Gemma read matched accuracy levels while running 1.9 to 5.1 times faster per decision. All per-item outputs and pre-registration documents were committed to a public GitHub repository before any model calls were made.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Engineer Applies Test-First Thinking to Requirements, Contracts, and Specs

Software engineer Anton, who works primarily with PHP/Symfony and Go, has written about extending test-driven development (TDD) principles beyond code to earlier stages of software work, including requirements and contracts. His core argument is that a checkable condition must be written before the thing it is meant to validate, otherwise it simply describes what was already built and cannot serve as a real gate. He illustrates this with a code coverage ratchet that prevents the recorded threshold from being lowered in pull requests, while honestly noting the bar is currently set at zero despite actual coverage sitting at 86.7%. A second example shows the approach working as intended, where a closing condition for a database-access refactor was written while the work was still in progress rather than after completion. Anton frames the method not as a testing philosophy but as a discipline around the order in which things are written down at all.

0 comments Read more at DEV Community