Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Jeff – Jev-compatible 0.8B decision models, trained at home, ~30 ms (github.com/firelex)
    129comments
  2. Pirating the Pirates (mubi.com)
    233comments
  3. 12,000-year-old Göbeklitepe burials explain scattered bones (archaeologymag.com)
    22comments
  4. MicroLLM Lab – Try 7 tiny LLM's in the browser (stateofutopia.com)
    66comments
  5. 1996 chat room simulator connected to Win95 and System 7 web desktops (lolchat.rip)
    21comments
  6. California farmers are struggling to sell grapes as demand for wine drops (kqed.org)
    191comments
  7. Scientists solve 1840s space weather mystery (arstechnica.com)
    38comments
  8. Sonnet 5.5 (anthropic.com)
    421comments
  9. Tank Body Problem (jimsitu.com)
    5comments
  10. ESP32S3 cluster running 1.58-bit (BitNet) Language model (github.com/low-zi-hong)
    5comments
  11. World Labs Is Joining AMD (worldlabs.ai)
    77comments
  12. Hijacking the PS5's RTMP stream (yashgarg.dev)
    67comments
  13. U.S. Strategic Petroleum Reserve Falls to Lowest Level Since 1982 (oilprice.com)
    1comments
  14. How to win a beer with high-dimensional statistics (jamiesimon.io)
    2comments
  15. Bluegraph – Explore NOAA buoy data, rebuilt in 3D from measured spectra (bluegraph.io)
    2comments
  16. Kids turned low-traffic NPR Spotify comments into a secret group chat (thisamericanlife.org)
    185comments
  17. What is the best shape of a city? Modelling effect of urban form on distance (sagepub.com)
    9comments
  18. Does Reddit have an astroturfing problem? What the data suggests (petervijeh.com)
    157comments
  19. It's Time to Investigate the AI Labs (calnewport.com)
    129comments
  20. Updated Google Maps shows destruction of the city of Rafah (twitter.com/aliabunimah)
    145comments
  21. Show HN: HN.watch – Videos of all Hacker News posts (hn.watch)
    82comments
  22. What reversing, modernising old games tells us about the economic impact of AI (isfine.org)
    28comments
  23. Nvidia wants to put a watchdog chip next to every AI agent (cnbc.com)
    152comments
  24. The Art Forger Who Became a National Hero (priceonomics.com)
    1comments
  25. Cf: The Agentic CLI for the Cloudflare API (cloudflare.com)
    56comments
  26. Blend and Haul: Fertilizer Blending Simulator (wedgworth.com)
    1comments
  27. Behold the pawpaw (cbc.ca)
    18comments
  28. Show HN: Destroy Any Website with Stickman (spritefusion.com)
    28comments
  29. First Steps of the PLC Organization – Independent Public Ledger of Credentials (plcred.org)
    19comments
  30. Coding is not solved (alexewerlof.com)
    442comments

2023 IG Report about Social Security Numberholders Age 100 or older [pdf]

2 pointsby 1y agooig.ssa.gov
6 comments
1y agoHN ↗

"The agency has not established a new system to properly annotate death information in its database, which included roughly 18.9m social security numbers of people born in 1920 or earlier but were not marked as deceased. This does not mean, however, that these individuals were receiving benefits.

The agency decided not to update the database because of the cost to do so, which would run upward of $9m."

https://www.theguardian.com/us-news/2025/feb/20/trump-social...

1y agoHN ↗

  > This does not mean, however, that these individuals were receiving benefits.

Does it mean that they are definitely NOT receiving benefits, though?

1y agoHN ↗

It's addressed in a foot note:

At the time of our review, approximately 44,000 of the 18.9 million number holders were receiving SSA payments.

It was mentioned earlier in the article there are 531 million SSN in the system total.

1y agoHN ↗

I feel like this game feels endless if folks just aren't curious and panic.

Yeah I got rows (or documents or whatever) in my database ... that's not bad, that could mean anything.

I don't prune DBs aggressively because that's dangerous, and honestly business logic covers things like "should do X,Y,Z" , not the existence of a row.

1y agoHN ↗

The birthdate in my SSA master record was wrong, and I discovered it only because the IRS upgraded their security (~10 years ago) and I could no longer file my taxes electronically - I couldn’t make it past the anti-fraud checks.

It took something like 2 years to track down the root cause (the SSA master record); the value they had stored looked a lot like a fat finger job by some data entry clerk back in the 1970s when I was born.

Fixing it took about 30 seconds at an actual SSA office building. I spent more time in the elevator.

Assuming everything in a computer is either correct or fraud is a terrible assumption when you are dealing with hundreds of millions of people in the real world.