Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Keys Not Included: recovering the signing keys for US driver's license barcodes(ryan.science ↗)
    15comments
  2. Nvidia announces native GPU programming in Rust(nvidia.com ↗)
    156comments
  3. Training a 4B model to produce 81% faster query plans than Postgres(rohanbansal.com ↗)
    91comments
  4. DeepSeek-v4.1 Flash: Pushing the Limits of KV Cache Compression(zartbot.github.io ↗)
    6comments
  5. Xiaomi Mimo 2.6 live post-training dashboard(xiaomi.com ↗)
    84comments
  6. Backups Aren't Simple(filipovski.net ↗)
    70comments
  7. Breaking the 1.58-bit Barrier for Ternary LLMs(arxiv.org ↗)
    22comments
  8. Small programming tricks(will-keleher.com ↗)
    198comments
  9. Developing provably correct Rust code with Verus(amazon.science ↗)
    7comments
  10. The Painful Truth: The RAM Crisis Is Only Just the Beginning(madshrimps.be ↗)
    4comments
  11. The engineering behind the US Strategic Petroleum Reserve(johnjwang.com ↗)
    56comments
  12. A 32-Year-Old Bug Walks into a Telnet Server(watchtowr.com ↗)
    discuss
  13. OpenSpec – A lightweight and configurable AI spec framework(openspec.dev ↗)
    38comments
  14. The Return of Sail Power: Cargo Ships Are Turning Back to the Wind(gcaptain.com ↗)
    17comments
  15. Performance Improvements in .NET 11(devblogs.microsoft.com/dotnet ↗)
    39comments
  16. PCB is brought to you by Fable 5(a6mzero.com ↗)
    13comments
  17. Reversing Factorio's RNG(gegell.github.io ↗)
    21comments
  18. AWS says it can't restore some data from mideast facilities struck by Iran(wsj.com ↗)
    235comments
  19. Part-human part-mouse brain developed in science breakthrough(bbc.com ↗)
    7comments
  20. HarnessTax: How Much Does the Harness Matter for Coding Agents?(harnesstax.github.io ↗)
    20comments
  21. Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations(github.com/arnegiacomo ↗)
    240comments
  22. Japan's book scene is moving from bookstores to libraries(untranslatedjp.substack.com ↗)
    53comments
  23. Mapsnap: Automated Georeferencing for Historic Sanborn Insurance Maps(danvk.org ↗)
    2comments
  24. Anecdotally, programmers dislike "reduce"(evanhahn.com ↗)
    181comments
  25. Reverse-engineered Jev-like model(github.com/vinnylarouge ↗)
    14comments
  26. Dream-RSI: Recursive Self-Improvement through Evolving Worlds(arxiv.org ↗)
    49comments
  27. Why Does the Universe Expand?(cosmicave.org ↗)
    29comments
  28. Anatomy of a Texture(agentlien.github.io ↗)
    14comments
  29. Monsanto's Cruel, and Dangerous, Monopolization on American Farming (2008)(vanityfair.com ↗)
    8comments
  30. The DeepMind Institute(deepmind.com ↗)
    53comments

Pangram – AI detector for text and images

20 pointsby 3h agopangram.com
15 comments
1h agoHN ↗

How accurate is this? I want to see a negative before i provide you with a positive.

1h agoHN ↗

An AI detector that actually works.

I detect Claude.

1h agoHN ↗

Interestingly checking good chunks of their site, it detects as 100% human

42m agoHN ↗

I mean, that's just the most direct way to say what they're saying? Doesn't smell Claudy to me.

Like, if I had an AI detector that actually worked—and all the other ones didn't, which they don't—I'd put it exactly the same way.

18m agoHN ↗

If I were your editor, I'd strike the adverb. It weakens the sentence.

47m agoHN ↗

I’m surprised at the current sentiment in the comments. Pangram is amazing and has really interesting engineering too. I would have guessed that reliably identifying LLM generated text was not possible without watermarks.

2m agoHN ↗

I would have guessed that reliably identifying LLM generated text was not possible

It depends what you mean by "reliably." If you mean, "we should be comfortable relying on this kind of tool at scale to identify and punish students, professionals, and writers who may have used AI," absolutely not.

If you take "reliably" to mean "1 in 200 false positive rate" as they disclose on their front page, absolutely that is possible (they are doing it today!).

Unfortunately their marketing is really insisting on the former, and trying to push it into the zeitgeist that detection of AI-generated or edited text is reliable-type-1 now and long-term. They fail to make it clear that this is merely a tool that strongly suggests text follows patterns known to us at the present time of known LLMs. However, that fingerprint will drift over time, as LLMs get better, human writing style evolves, and the line between human and "smart autocorrect" becomes even blurrier (does speech-to-text push the model into "AI assisted" mode, because it tidied up your punctuation, for example?)

"What color are your bits" is good reading today as it was 20 years ago: https://ansuz.sooke.bc.ca/entry/23

43m agoHN ↗

People expect a binary response, is it AI generated yes or no. But it's more complicated than that. For example, if you see an emdash, it's probably AI generated. But it can also mean the author used it for fixing grammar or tenses. LLMs can't help but try to help. The same for it's not X, but Y. Sure it's a known pattern, but it's not like people don't use this trope all the time.

In my experience, Pangram is great for detecting an author who is trying to pass someone else's work as theirs, or if they are tackling a subject they have little to no knowledge in.

24m agoHN ↗

I don't work for Pangram, but I do a lot of writing at work. API docs, blogs, code, tweets, linkedin, all that.

If you've tried AI detectors a couple years ago, they're basically in the same position that coding agents were a few years ago, where everyone was skeptical at first, but the tech has gotten a lot better. Give it a shot, it's quite good. They are slightly tuned a bit towards classifying things as AI, but I imagine that's deliberate.

The only thing is that their models are pricey, but, very useful.

13m agoHN ↗

I didn't want to shell out $20 a month for the general thing, so I spent $90 on data collection and built my own for code comments specifically. It runs locally in your browser with a relatively small classification model trained on classical stylometric features. You can try that before turning to Pangram for uncertain cases, if you wish.[1]

It's easy to get high accuracy numbers if you're testing on long (50+ words) texts. Much harder when the documens are short, as code comments tend to be.[2]

[1]: https://xkqr.org/aicomment

[2]: https://entropicthoughts.com/better-ai-comment-classifier

8m agoHN ↗

Based on their methodology it looks like the accuracy figures (99.82% for Opus 5) are the true positive rate rather than a combined metric that factors in the false positive rate as well. They claim 1 in 10,000 but it would be nice if we had a per-model breakdown for that specific test.

2m agoHN ↗

First they sell the problem, then they sell solution to that problem.