Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Jemalloc 5.4.0(github.com/jemalloc ↗)
    36comments
  2. The scourge of x86 emulation(fex-emu.com ↗)
    20comments
  3. Astra for Law(openai.com ↗)
    521comments
  4. Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint(prismml.com ↗)
    127comments
  5. Bend – A language that blocks AI mistakes via proof, on CPU and GPU(bend-lang.com ↗)
    215comments
  6. Qwen 3.8 Omni Flash(qwen.ai ↗)
    78comments
  7. When the fractional part of a float fixes your shader(crocidb.com ↗)
    1comments
  8. Hister: A private search engine for the pages you visit and the files you keep(github.com/asciimoo ↗)
    163comments
  9. Wax motor(wikipedia.org ↗)
    69comments
  10. Pre-Greek: The lost language hidden within Ancient Greek(linguisticdiscovery.com ↗)
    33comments
  11. Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA(global.fujitsu ↗)
    227comments
  12. A heap overflow and SSO misconfiguration to compromise OpenAI internal repos(hacktron.ai ↗)
    144comments
  13. Shapelearn Qwen 3.8 27B (13.1 GB VRAM)(byteshape.com ↗)
    7comments
  14. How to Write with an LLM(sockpuppet.org ↗)
    92comments
  15. Ask A Monk – A digital wilderness for thoughts with no immediate answer(askamonk.online ↗)
    23comments
  16. Why Does the Universe Expand?(cosmicave.org ↗)
    50comments
  17. Flet 1.0 – Build cross-platform apps in Python(flet.dev ↗)
    56comments
  18. Telstra outage: The night a network decided the year was 2006(netnod.se ↗)
    23comments
  19. Diplodocus, Long Thought Exclusively American, Turns Up in Spain(sci.news ↗)
    37comments
  20. Speeding up gearhash on ARM64(sam.dev ↗)
    discuss
  21. Why I didn’t sign the Fields medallists’ letter(gowers.wordpress.com ↗)
    366comments
  22. Apple detectives solved mystery of ancient tree and rewrote the history of fruit(scientificamerican.com ↗)
    9comments
  23. Fixing an NZXT Signal 4K30 part 2: the green/pink video bug(downtowndougbrown.com ↗)
    10comments
  24. CrowdSec Source Code Leak(crowdsec.net ↗)
    47comments
  25. The most important product decision is what you don't build(liamnugent.me ↗)
    36comments
  26. How do we prevent mathemathics from devolving into the Medieval Era of secrecy?(mathoverflow.net ↗)
    105comments
  27. Show HN: Snapdrop: Instantly share files between devices. No setup, no signup(snapdrop.me ↗)
    34comments
  28. Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data(arxiv.org ↗)
    39comments
  29. How Uber Protects Against Retry Storms(uber.com ↗)
    41comments
  30. Khipu (Quipu) Field Guide(khipufieldguide.com ↗)
    discuss

Ask HN: Two unlabeled downvote buttons rather than one

4 pointsby 5y ago
2 comments
Hear me out. Regardless of the rules, everyone has their own personal reasons for downvoting a post. With a single bit, there's no way to discover the hidden rules that people use to express their reaction to a post.

Labeling the downvote buttons (e.g. "makes me feel sad|bad|mad") has been suggested in the past, but we all know that the expressed semantics of the buttons will be ignored by the community.

Suppose, however, that HN adds one additional unlabeled downvote button.

Faced with two unlabelled downvote buttons, would you click both? When would you click one but not the other? Would one turn into the quality downvote while the other turned into the feelings downvote?

5y agoHN ↗

Would one turn into the quality downvote while the other turned into the feelings downvote?

No, they wouldn't. The problem is that if considered intrapersonal, different buttons could get different qualities, but when considered interpersonal they probably wouldn't.

There are different possible ways to fill multiple downvote buttons with a sense. For example, it could be "feelings downvote" and "quality downvote". Or "quality downvote" and "feelings downvote" from left to right. Or it could be "slight downvote" and "strong downvote" and "slight+strong downvote" which is even stronger. Different people will use buttons differently, so in average it would be the same mess. Probably if a PhD dug into the raw data, she could make sense from it by categorizing downvoters and summing up their votes with normalizing coefficients, but I'm not sure.

Lichess recently changed their puzzles and forced me to vote for each puzzle. I really do not know which puzzle is good and which is not. I struggled to find a way to vote, and finally came to a simple strategy "upvote each puzzle", because I do not know any better. I'm sorry I did it, I wish to help lichess, but do not know how to. When faced with two downvote buttons I probably would struggle to make sense of it, then I'd find some simple strategy which I could verbalize and stick to it. It would be improbable, that the strategy would be "feelings" vs "quality", because how could I separate my feelings from a perceived quality?

5y agoHN ↗

It just doesn't matter that much. No one (well, save literally a single person) can even see vote totals. Votes do one thing—make comments more or less prominent within a thread.

I see voting as a sort of collective curation mechanism, and I vote accordingly. If I see a insightful comment that I think more people should read, I upvote it. If I see a dumb comment I think less people should read, I downvote it. Assuming others agree with me, the insightful comments end up higher in the thread, and the stupid ones become faded and easy to ignore.