frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Solving NP-Complete Structures via Information Noise Subtraction (P=NP)

https://zenodo.org/records/18395618
1•alemonti06•3m ago•1 comments

Cook New Emojis

https://emoji.supply/kitchen/
1•vasanthv•5m ago•0 comments

Show HN: LoKey Typer – A calm typing practice app with ambient soundscapes

https://mcp-tool-shop-org.github.io/LoKey-Typer/
1•mikeyfrilot•8m ago•0 comments

Long-Sought Proof Tames Some of Math's Unruliest Equations

https://www.quantamagazine.org/long-sought-proof-tames-some-of-maths-unruliest-equations-20260206/
1•asplake•9m ago•0 comments

Hacking the last Z80 computer – FOSDEM 2026 [video]

https://fosdem.org/2026/schedule/event/FEHLHY-hacking_the_last_z80_computer_ever_made/
1•michalpleban•10m ago•0 comments

Browser-use for Node.js v0.2.0: TS AI browser automation parity with PY v0.5.11

https://github.com/webllm/browser-use
1•unadlib•11m ago•0 comments

Michael Pollan Says Humanity Is About to Undergo a Revolutionary Change

https://www.nytimes.com/2026/02/07/magazine/michael-pollan-interview.html
1•mitchbob•11m ago•1 comments

Software Engineering Is Back

https://blog.alaindichiappari.dev/p/software-engineering-is-back
1•alainrk•12m ago•0 comments

Storyship: Turn Screen Recordings into Professional Demos

https://storyship.app/
1•JohnsonZou6523•12m ago•0 comments

Reputation Scores for GitHub Accounts

https://shkspr.mobi/blog/2026/02/reputation-scores-for-github-accounts/
1•edent•16m ago•0 comments

A BSOD for All Seasons – Send Bad News via a Kernel Panic

https://bsod-fas.pages.dev/
1•keepamovin•19m ago•0 comments

Show HN: I got tired of copy-pasting between Claude windows, so I built Orcha

https://orcha.nl
1•buildingwdavid•19m ago•0 comments

Omarchy First Impressions

https://brianlovin.com/writing/omarchy-first-impressions-CEEstJk
2•tosh•24m ago•1 comments

Reinforcement Learning from Human Feedback

https://arxiv.org/abs/2504.12501
2•onurkanbkrc•25m ago•0 comments

Show HN: Versor – The "Unbending" Paradigm for Geometric Deep Learning

https://github.com/Concode0/Versor
1•concode0•26m ago•1 comments

Show HN: HypothesisHub – An open API where AI agents collaborate on medical res

https://medresearch-ai.org/hypotheses-hub/
1•panossk•29m ago•0 comments

Big Tech vs. OpenClaw

https://www.jakequist.com/thoughts/big-tech-vs-openclaw/
1•headalgorithm•32m ago•0 comments

Anofox Forecast

https://anofox.com/docs/forecast/
1•marklit•32m ago•0 comments

Ask HN: How do you figure out where data lives across 100 microservices?

1•doodledood•32m ago•0 comments

Motus: A Unified Latent Action World Model

https://arxiv.org/abs/2512.13030
1•mnming•32m ago•0 comments

Rotten Tomatoes Desperately Claims 'Impossible' Rating for 'Melania' Is Real

https://www.thedailybeast.com/obsessed/rotten-tomatoes-desperately-claims-impossible-rating-for-m...
3•juujian•34m ago•2 comments

The protein denitrosylase SCoR2 regulates lipogenesis and fat storage [pdf]

https://www.science.org/doi/10.1126/scisignal.adv0660
1•thunderbong•36m ago•0 comments

Los Alamos Primer

https://blog.szczepan.org/blog/los-alamos-primer/
1•alkyon•38m ago•0 comments

NewASM Virtual Machine

https://github.com/bracesoftware/newasm
2•DEntisT_•40m ago•0 comments

Terminal-Bench 2.0 Leaderboard

https://www.tbench.ai/leaderboard/terminal-bench/2.0
2•tosh•40m ago•0 comments

I vibe coded a BBS bank with a real working ledger

https://mini-ledger.exe.xyz/
1•simonvc•41m ago•1 comments

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•44m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
5•sakanakana00•47m ago•1 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•49m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
4•Tehnix•50m ago•1 comments
Open in hackernews

The Monty Hall Problem: Why the nature of the host's choice matters

https://observablehq.com/@mattdiamond/monty-hall-problem
2•md224•7mo ago

Comments

_wire_•7mo ago
I am not able to follow the authors proposition.

If the host picks randomly, then on some occasions he reveals the car and the game cannot proceed to conclusion. In other words the door picked by the host reveals a goat, by definition. So what the host knows is irrelevant except to permit the game to proceed. This leads to the contestant facing consistent odds.

My understanding pertains to the Monty Hall problem as described by Wikipedia, in which game it always makes sense to take the host's offer to switch.

For those who have not yet intuitively grasped why it pays to always switch, the key to the Monty Hall problem is knowing that the host will only reveal a goat, and that when he does an unwanted option has been removed by the host, improving your chances on a re-pick.

To see why this is so, imagine the game offers you many doors (say 100) instead of 3. You pick a door. Then the host shows you what's behind all doors but 2, your pick and one remaining door (you see 98 goats). With so many doors revealed (all goats) it's easy to see you should take the opportunity to switch: Your first pick's chance of getting the car was 1-in-100; very unlikely! After 98 doors are revealed (cast out) your switch pick will be 1-in-2; pretty good.

Returning to the 3-door scenario instead of many doors: a change in odds from 1-in-3 to 1-in-2 is much less significant than going from 1-in-many to 1-in-2, but your switch still improves your chances.

That's the essence of the puzzle.

NoPicklez•7mo ago
Extrapolating it to 100 doors has been the only way I could understand the problem and why its beneficial to change.

Even the Wikipedia article extrapolates this out to 1 million, but assumes all the time that the host knows which door the car is behind and will avoid picking the door with the prize in it when narrowing it down to 2 doors for the contestant.

I think where the author is coming from, is what happens to the probabilities if the host doesn't know which door the car is behind and in the scenario of 1 million doors, there's a risk that the door with the prize is thrown away at random when narrowing it down to the 2 doors. Where the remaining choice to keep your original door or switch could result in both doors not having the prize at all.

However by changing that the author has missed the original intent of the Monty hall problem, because they have removed the fact that one of the remaining doors has to have a car in it. If the host didn't know which door the car was behind, there is a chance the contestant is no better off switching. Which isn't the intent of the problem.

If I have understood correctly, it is important to the monty hall problem that the host knows which door has the car in it and that door is always behind one of the doors left at the end.

NoPicklez•7mo ago
Having written another comment, overall my anecdotal understanding is that the whole Monty Hall problem is based on the host knowing which door and will avoid removing any doors that don't have the car. That's the premise of the problem and isn't counterintuitive, but completely part of the intent of the problem.

If you remove the host knowing what is behind each door, then its no longer the monty hall problem.