Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Cloudflare Quick Tunnels(cloudflare.com ↗)
    44comments
  2. An Empirical Study of Harness Design for Coding Agents(arxiv.org ↗)
    23comments
  3. North Korean nuclear test sets off years of earthquakes(science.org ↗)
    27comments
  4. Show HN: Rickub – The Smartest Git in the Universe(rickub.com ↗)
    2comments
  5. OpenJev(openjev.com ↗)
    191comments
  6. Bend 2 and the Vibe-Coding Trap(liampwll.com ↗)
    191comments
  7. I don't like passkeys(hawksley.dev ↗)
    389comments
  8. The Shadows Lurking in the Equations – Underwater Islands(gods.art ↗)
    7comments
  9. Mathematicians Build Long-Awaited Graph Sandwich(quantamagazine.org ↗)
    discuss
  10. GrassLobster: AI Agentic Generation of Parametric Geometry Workflows(miro.vision ↗)
    discuss
  11. NATS publishes preliminary report on technical incident of 8 September(nats.aero ↗)
    11comments
  12. Build Faster Feedback Loops Using Qualitative User Research(nseldeib.com ↗)
    discuss
  13. Jemalloc 5.4.0(github.com/jemalloc ↗)
    65comments
  14. Cekura (YC F24) Is Hiring(ycombinator.com ↗)
    discuss
  15. The scourge of x86 emulation(fex-emu.com ↗)
    62comments
  16. Warren Buffett Steps Down as Berkshire Chairman, Names Son to Replace Him(nytimes.com ↗)
    128comments
  17. Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint(prismml.com ↗)
    172comments
  18. Bend – A language that blocks AI mistakes via proof, on CPU and GPU(bend-lang.com ↗)
    283comments
  19. ZCode, the GLM coding agent, silently uploads your Git history(tokenstead.ai ↗)
    53comments
  20. BeanShell3 in Development(beanshell.github.io ↗)
    6comments
  21. Qwen 3.8 Omni Flash(qwen.ai ↗)
    106comments
  22. Microsoft exec called AI scraping 'the largest theft of labor in human history'(techcrunch.com ↗)
    557comments
  23. Second Circuit Allows Government to Search Electronic Devices at the Border(knightcolumbia.org ↗)
    26comments
  24. When the fractional part of a float fixes your shader(crocidb.com ↗)
    16comments
  25. How to Write with an LLM(sockpuppet.org ↗)
    174comments
  26. Pre-Greek: The lost language hidden within Ancient Greek(linguisticdiscovery.com ↗)
    57comments
  27. HEIF Heist: image parser RCE exploit(heif-heist.com ↗)
    1comments
  28. Replacing Pull Requests with Delta(zed.dev ↗)
    59comments
  29. I Vibed a Proof of Conway's Conjecture(overreacted.io ↗)
    68comments
  30. New wild cat species discovered – with only one known living member(bbc.com ↗)
    8comments

A Plea for Responsible and Contextualized Reporting on User Security

62 pointsby 9y agotechnosociology.org
6 comments
9y agoHN ↗

With just a few exceptions, the people who signed this are sort of a who's-who of practical cryptographic research and, in particular, of research into cryptographic backdoors.

9y agoHN ↗

If that can help, I agree with "this particular issue is not a backdoor".

9y agoHN ↗

The latest episode of Risky Business podcast (risky.biz) had a good section with Alec Muffatt about this too.[0]

It's well worth listening to, with Alec being both considerate and colourful at the same time.

Disclaimer: regular listener, otherwise not affiliated.

0: http://risky.biz/RB439

9y agoHN ↗

https://twitter.com/zeynep/status/822301430933573632

The responses here are telling. The reasoning of a lot of people seems to be "WhatsApp isn't perfect, we should tell people not to use WhatsApp" without serious enough consideration what alternatives are actually likely to be usable and/or used.

Good example of "perfect is the enemy of good". In my experience this kind of behavior is extremely common in the security/privacy space, and it is exceptionally harmful to getting real user improvements out (which tend to require measured compromises).

9y agoHN ↗

Caveat -- personal reaction opinion, off the cuff:

If casual use is at stake, and you could care less about your metadata / network graph, agree with the gist, WhatsApp is fine, better than most options.

But Author's narrative shifts UX "Personas" multiple times, appealing to one Persona (general public) to argue for low friction usability, prioritizing delivery over confidentiality, and a different Persona who is under real (dismissively called 'imagined' when it is not imaginary) threat when talking about need for confidentiality and deniability (quote: 'very few people are the kind of “high risk” users that EFF refers to–and such users have very different considerations').

Even as the 'journalist talking to the public' persona, your sources graph is recognized as important enough that journalists will go to jail to protect it.

If you are one of the very few with 'different considerations', then (a) the original concerns are not wrong, and (b) switching your behavior based on a given message's stakes is probably bad.

And if you are one of the few, having people with nothing to hide more broadly adopt the less common apps too is healthy, as then they are not only used for dissembling.

Railing against Signal or other apps prioritizing C & I over A as less usable than WhatsApp doesn't further that end for Personas with something to lose.