frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: A unique twist on Tetris and block puzzle

https://playdropstack.com/
1•lastodyssey•22s ago•0 comments

The logs I never read

https://pydantic.dev/articles/the-logs-i-never-read
1•nojito•1m ago•0 comments

How to use AI with expressive writing without generating AI slop

https://idratherbewriting.com/blog/bakhtin-collapse-ai-expressive-writing
1•cnunciato•2m ago•0 comments

Show HN: LinkScope – Real-Time UART Analyzer Using ESP32-S3 and PC GUI

https://github.com/choihimchan/linkscope-bpu-uart-analyzer
1•octablock•3m ago•0 comments

Cppsp v1.4.5–custom pattern-driven, nested, namespace-scoped templates

https://github.com/user19870/cppsp
1•user19870•4m ago•1 comments

The next frontier in weight-loss drugs: one-time gene therapy

https://www.washingtonpost.com/health/2026/01/24/fractyl-glp1-gene-therapy/
1•bookofjoe•7m ago•1 comments

At Age 25, Wikipedia Refuses to Evolve

https://spectrum.ieee.org/wikipedia-at-25
1•asdefghyk•9m ago•3 comments

Show HN: ReviewReact – AI review responses inside Google Maps ($19/mo)

https://reviewreact.com
2•sara_builds•10m ago•1 comments

Why AlphaTensor Failed at 3x3 Matrix Multiplication: The Anchor Barrier

https://zenodo.org/records/18514533
1•DarenWatson•11m ago•0 comments

Ask HN: How much of your token use is fixing the bugs Claude Code causes?

1•laurex•14m ago•0 comments

Show HN: Agents – Sync MCP Configs Across Claude, Cursor, Codex Automatically

https://github.com/amtiYo/agents
1•amtiyo•15m ago•0 comments

Hello

1•otrebladih•17m ago•0 comments

FSD helped save my father's life during a heart attack

https://twitter.com/JJackBrandt/status/2019852423980875794
2•blacktulip•19m ago•0 comments

Show HN: Writtte – Draft and publish articles without reformatting, anywhere

https://writtte.xyz
1•lasgawe•21m ago•0 comments

Portuguese icon (FROM A CAN) makes a simple meal (Canned Fish Files) [video]

https://www.youtube.com/watch?v=e9FUdOfp8ME
1•zeristor•23m ago•0 comments

Brookhaven Lab's RHIC Concludes 25-Year Run with Final Collisions

https://www.hpcwire.com/off-the-wire/brookhaven-labs-rhic-concludes-25-year-run-with-final-collis...
2•gnufx•25m ago•0 comments

Transcribe your aunts post cards with Gemini 3 Pro

https://leserli.ch/ocr/
1•nielstron•29m ago•0 comments

.72% Variance Lance

1•mav5431•30m ago•0 comments

ReKindle – web-based operating system designed specifically for E-ink devices

https://rekindle.ink
1•JSLegendDev•32m ago•0 comments

Encrypt It

https://encryptitalready.org/
1•u1hcw9nx•32m ago•1 comments

NextMatch – 5-minute video speed dating to reduce ghosting

https://nextmatchdating.netlify.app/
1•Halinani8•33m ago•1 comments

Personalizing esketamine treatment in TRD and TRBD

https://www.frontiersin.org/articles/10.3389/fpsyt.2025.1736114
1•PaulHoule•34m ago•0 comments

SpaceKit.xyz – a browser‑native VM for decentralized compute

https://spacekit.xyz
1•astorrivera•35m ago•0 comments

NotebookLM: The AI that only learns from you

https://byandrev.dev/en/blog/what-is-notebooklm
2•byandrev•35m ago•1 comments

Show HN: An open-source starter kit for developing with Postgres and ClickHouse

https://github.com/ClickHouse/postgres-clickhouse-stack
1•saisrirampur•36m ago•0 comments

Game Boy Advance d-pad capacitor measurements

https://gekkio.fi/blog/2026/game-boy-advance-d-pad-capacitor-measurements/
1•todsacerdoti•36m ago•0 comments

South Korean crypto firm accidentally sends $44B in bitcoins to users

https://www.reuters.com/world/asia-pacific/crypto-firm-accidentally-sends-44-billion-bitcoins-use...
2•layer8•37m ago•0 comments

Apache Poison Fountain

https://gist.github.com/jwakely/a511a5cab5eb36d088ecd1659fcee1d5
1•atomic128•39m ago•2 comments

Web.whatsapp.com appears to be having issues syncing and sending messages

http://web.whatsapp.com
1•sabujp•39m ago•2 comments

Google in Your Terminal

https://gogcli.sh/
1•johlo•40m ago•0 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.