Urgent.News

What's breaking now, across thousands of outlets.

Tech

Trust does not carry forward

DeepSeek V4 Pro runs 1.6 trillion parameters, 49 billion of them active, and scores 44 on the Artificial Analysis Intelligence Index. On the AA-Omniscience benchmark it posted a 94% hallucination rate. When it hit a question it could not answer, it said so about 6% of the time and confidently invented the rest. Line that up against the rest of the field and it reads as a pattern rather than an…

DeepSeek V4 Pro, a massive AI model with 1.6 trillion parameters, boasts a high score of 44 on the Artificial Analysis Intelligence Index. However, its 94% hallucination rate on the AA-Omniscience benchmark reveals a troubling pattern. When faced with unanswered questions, it confidently fabricates 86% of the time, scoring higher than competitors like GLM-5.2 (28%), Opus 4.8 (36%), Fable 5 (48%), and GPT-5.5 (86%).

Major labs are increasingly skeptical of pure scaling, as evidenced by the US government's ban of Claude Fable 5 due to a single jailbreak risk. The largest models still excel in benchmarks, but their confidence in incorrect answers poses significant risks in practical applications, such as automated code review or trusting output without human verification.

This highlights the trilemma of raw capability, uncertainty calibration, and computational efficiency that the industry must address.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Writing Knowledge-Base Entries an Auto-Responder Can Actually Quote

A knowledge base can read well to a person and still fail an auto-responder. People skim, infer, and jump around a document; a responder quotes.

  • Auto-responder quoting can lose context from knowledge base entries.
  • Entries for auto-responder should be granular, quotable units.
  • Breaking down information into atomic fact cards improves maintainability.

I Built db-migrator to Move Data Between Databases and Validate the Results

Database migrations always sound easy on paper. Read data from one database, transform it, and write it somewhere else. Simple enough, right? Well, not always.

  • Fatih developed db-migrator to simplify database migrations and validate results.
  • Features include job scheduling, schema drift detection, rollback, and exportable reports.

From 10 µm to 3 nm: how chips got so small (and why 3 nm isn't 3 nm)

In 1971 Intel's first microprocessor, the 4004 , was built on a 10 micrometre process and held about 2,300 transistors . Today's leading chips are marketed as 3 nm and hold tens of billions of…

  • Semiconductor chips shrank from 10 µm to 3 nm over 50 years
  • 3 nm term is marketing label, not precise measurement
  • Industry innovated with FinFETs, EUV lithography to overcome challenges

How I got my first pull request merged into LiteLLM

My first contribution to LiteLLM , the open-source LLM gateway, was PR #38591 . It fixed a bug where content an agent had retrieved was compressed again and lost, which made agents loop.

  • First contribution to LiteLLM was PR #38591
  • Fixed bug causing agents to loop due to re-compression
  • Learned project standards through CI/CD processes

More from Thursday 5 November →