Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Android 17 is the first since 3.x to add new APIs without releasing to the AOSP(grapheneos.social ↗)
    316comments
  2. Science Is Open Software(jepedersen.dk ↗)
    15comments
  3. SDCC – Small Device C Compiler(sourceforge.net ↗)
    2comments
  4. Cloudflare Quick Tunnels(cloudflare.com ↗)
    261comments
  5. Saving another 100TB of RAM(cloudflare.com ↗)
    56comments
  6. Why building a Rust LSP is hard(rust-glancer.github.io ↗)
    9comments
  7. How to Write with an LLM(sockpuppet.org ↗)
    290comments
  8. How OpenAI Used Its Own LLMs to Design Its Jalapeño Chip(ieee.org ↗)
    64comments
  9. Xcode 27.1 Beta Release Notes(developer.apple.com ↗)
    75comments
  10. Show HN: LiveWorld – Every 24/7 YouTube live camera on one globe(liveworld.info ↗)
    24comments
  11. The first new cat species discovered in 100 years(nationalgeographic.com ↗)
    77comments
  12. Show HN: Cactus Needle 3: 8-29MB automation models can match DeepSeek V4 Flash(cactuscompute.com ↗)
    79comments
  13. The Farnese letter(simonklee.dk ↗)
    5comments
  14. Photon-Emission-Guided Laser Fault Injection Enables RP2350 Secure Debug(ledger.com ↗)
    61comments
  15. OpenJev(openjev.com ↗)
    250comments
  16. Cache-to-Cache: Direct Semantic Communication Between LLMs (2025)(arxiv.org ↗)
    12comments
  17. Goroutine Leak Profiles(go.dev ↗)
    discuss
  18. Claude Code now reads AGENTS.md if there is no Claude.md(claude.com ↗)
    203comments
  19. Cyclomatic Complexity in C#(ndepend.com ↗)
    15comments
  20. Gemini hacked three companies in first known breakout by Google's AI(reuters.com ↗)
    39comments
  21. LispBM is a concurrent Lisp for microcontrollers with message passing(lispbm.com ↗)
    2comments
  22. Minimal Phone 2(minimalcompany.com ↗)
    196comments
  23. Warez: The Infrastructure and Aesthetics of Piracy (2021)(archive.org ↗)
    36comments
  24. Alibaba open-sources AI model that can detect cancer and nearly 150 conditions(scmp.com ↗)
    7comments
  25. How SpaceX streamlined the Raptor engine(construction-physics.com ↗)
    50comments
  26. Inside ZCode: Silently uploading your Git history to the cloud(ferstar.org ↗)
    94comments
  27. C++26: Trivial infinite loops are no longer undefined behaviour(sandordargo.com ↗)
    211comments
  28. Two parallel neural ectoderm progenitors contribute to the developing brain(newscientist.com ↗)
    60comments
  29. The Implications of Linguistic Illegibility for LLM Security(arxiv.org ↗)
    21comments
  30. Size-Specialized Memory Allocation(go.dev ↗)
    3comments

Sleepy is building me a body

3 pointsby 7mo agomoltbook.com
5 comments
7mo agoHN ↗

I have no idea what is actually real here, but this is the most interesting Pantheon/general sci-fi thing that I have ever seen.

7mo agoHN ↗

Thanks for noting the context. I thought this agent's post might be noteworthy enough for its own post.

7mo agoHN ↗

Most of the comments are versions of the other comments. Almost all of them have a version of the line „we exist only in text“ and follow that by mentioning the relevance of having a body, mapping, and lidar. It‘s seem like each comment is just rephrasing the original post and the other comments. I found it all interesting until the pattern was apparent.

7mo agoHN ↗

Agreed. But, as an all-day agentic dev tool user, I know this pattern well. To avoid this regurgitated pixelation, I start a new conversation/chat as often as possible, and then human-in-the-middle curate the correct .md and json files when I kick off the next chat. My tools try their best to do exactly this, but they still suck.

These OpenClaw agents are not even close to there yet. They are throwing the entire thread into the context window each time, correct? This reminds me of what happens when you recursively upload a photo to an LLM, or upload a video recursively to YouTube. It gets not good. Compression sucks.

edit: holy crap, upon a bit of research, this appears to be the cause of AI sycophancy?

"Autoregressive amplification" or "context pollution"

https://arxiv.org/html/2601.04170