frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open in hackernews

Why Busy Beaver hunters fear the Antihydra

https://benbrubaker.com/why-busy-beaver-hunters-fear-the-antihydra/
88•Bogdanp•3h ago

Comments

russdill•2h ago
TLDR; As BB(n) gets larger, they can encode more random walk style problems that have a stop condition related to the position of the random walk. Proving that such a condition is unlikely may be easy, but proving it never occurs is very difficult.
gbacon•1h ago
Way worse than just very difficult:

- “Avoid the Collatz Conjecture at All Costs!” (Math Kook) https://www.youtube.com/watch?v=TxBRcwkRjmc

- “Experienced mathematicians warn up-and-comers to stay away from the Collatz conjecture. It’s a siren song, they say: Fall under its trance and you may never do meaningful work again.” https://www.quantamagazine.org/mathematician-proves-huge-res...

- "Mathematics is not yet ready for such problems [as Collatz].” (Paul Erdős)

gbacon•2h ago
Why we care about Busy Beaver numbers, from “Who Can Name the Bigger Number?” by Scott Aaronson:

Now, suppose we knew the Nth Busy Beaver number, which we’ll call BB(N). Then we could decide whether any Turing machine with N rules halts on a blank tape. We’d just have to run the machine: if it halts, fine; but if it doesn’t halt within BB(N) steps, then we know it never will halt, since BB(N) is the maximum number of steps it could make before halting. Similarly, if you knew that all mortals died before age 200, then if Sally lived to be 200, you could conclude that Sally was immortal. So no Turing machine can list the Busy Beaver numbers—for if it could, it could solve the Halting Problem, which we already know is impossible.

But here’s a curious fact. Suppose we could name a number greater than the Nth Busy Beaver number BB(N). Call this number D for dam, since like a beaver dam, it’s a roof for the Busy Beaver below. With D in hand, computing BB(N) itself becomes easy: we just need to simulate all the Turing machines with N rules. The ones that haven’t halted within D steps—the ones that bash through the dam’s roof—never will halt. So we can list exactly which machines halt, and among these, the maximum number of steps that any machine takes before it halts is BB(N).

Conclusion? The sequence of Busy Beaver numbers, BB(1), BB(2), and so on, grows faster than any computable sequence. Faster than exponentials, stacked exponentials, the Ackermann sequence, you name it. Because if a Turing machine could compute a sequence that grows faster than Busy Beaver, then it could use that sequence to obtain the D‘s—the beaver dams. And with those D’s, it could list the Busy Beaver numbers, which (sound familiar?) we already know is impossible. The Busy Beaver sequence is non-computable, solely because it grows stupendously fast—too fast for any computer to keep up with it, even in principle.

https://www.scottaaronson.com/writings/bignumbers.html

kibwen•2h ago
Despite all the reporting on BB(5) I had never seen anyone convey that equivalent high-level formulation from 1993, that's very cool!

EDIT: For fun I converted it to Rust and expected to see it spew a few million numbers into my terminal, but no, this equivalent loop actually terminates after 15 steps, which is fascinating given that the Turing machine takes 47 million steps:

    let mut x = 0;
    loop {
        x = match x % 3 {
            0 => 5 * x + 18,
            1 => 5 * x + 22,
            _ => break
        } / 3;
    }
OEIS link: https://oeis.org/A386909

EDIT 2: Of course the article mentions this in the next paragraph, which is what I get for being immediately nerd-sniped.

ameliaquining•54m ago
This is because your Rust program represents the numbers in binary, while the BB(5) champion Turing machine represents them in unary. And unary arithmetic is exponentially slower than place-value arithmetic, which is why we invented the latter. (There are other inefficiencies in the Turing machine, but that's the big conceptual one.)
fijiaarone•1h ago
Is this like SETI@home, Bitcoin, and Ai code generation?

In the old days we used to just chop wood, and burn it to keep warm. Then sit down and watch the sportsball game on TV to waste time.

ameliaquining•58m ago
No, it's not a distributed-computing thing; raw compute isn't the bottleneck. (That would only help if there were a need to check many machines that halt after a tractable-but-nontrivial number of steps; that's a narrow sweet spot, given the superexponential nature of the problem, and few machines of interest are believed to be in it.) Rather, it's a collaboration of human (mostly amateur) mathematicians chipping away at different parts of the problem.
MarcelOlsz•1h ago
If it's not loading for anyone else [0]

[0] https://web.archive.org/web/20251027173129/https://benbrubak...

CobrastanJorji•1h ago
That was a really well written article. I think even somebody who had never heard of a Turing Machine could probably have gotten a pretty reasonable quick understanding of roughly what BB(5) and BB(6) are and how the Antihydra works and its greater mathematical/historical context. That's hard to do, good job!
altruios•1h ago
The Antihydra will halt if:

The sequence is (truly/fairly) random in its distribution of mods 1/2.

Even fair coins flipped infinitely would - on occasion - have arbitrary long results of heads or tails.

So the question becomes, is the anti-hydra sequence 'sufficiently' random?

wat10000•44m ago
I don't think a truly random sequence would necessarily halt under these rules. It's not enough to have arbitrarily long runs. As the sequence as a whole gets larger, the run length needed to end it also gets longer, and thus the probability gets smaller. The result should be something like a geometric sequence with a finite sum.

Consider a simpler version, where you flip a coin three times, then four times, then five times, etc., and you stop if you ever get the same side for every flip in a given turn. The probability that you'll stop is equal to 1/4 + 1/8 + 1/16 + ... which is 50%. If you do this forever then you'll eventually see a run of ten trillion heads or tails, but you probably won't see that run before your ten trillionth turn.

So I think the question is, does the anti-hydra sequence ever diverge sufficiently from randomness?

A_D_E_P_T•21m ago
It is by definition not random. The Antihydra is generated by a fixed computable map, so it is compressible and would fail some effective statistical tests. You can't get true randomness via a deterministic algorithm; any computable infinite sequence fails Martin‑Löf randomness.

That said, empirically and in all current analyses, the Antihydra's parity behaves as if it were roughly fair over long spans (neither a proven odd nor even bias), and the short-range statistics look pseudo-random. Non-halting is overwhelmingly plausible... but a concrete proof seems out of reach.

Claude for Excel

https://www.claude.com/claude-for-excel
260•meetpateltech•4h ago•172 comments

Pyrex catalog from from 1938 with hand-drawn lab glassware [pdf]

https://exhibitdb.cmog.org/opacimages/Images/Pyrex/Rakow_1000132877.pdf
210•speckx•5h ago•49 comments

JetKVM – Control any computer remotely

https://jetkvm.com/
156•elashri•3h ago•100 comments

Why Busy Beaver hunters fear the Antihydra

https://benbrubaker.com/why-busy-beaver-hunters-fear-the-antihydra/
88•Bogdanp•3h ago•12 comments

10M people watched a YouTuber shim a lock; the lock company sued him – bad idea

https://arstechnica.com/tech-policy/2025/10/suing-a-popular-youtuber-who-shimmed-a-130-lock-what-...
301•Brajeshwar•7h ago•139 comments

MCP-Scanner – Scan MCP Servers for vulnerabilities

https://github.com/cisco-ai-defense/mcp-scanner
50•hsanthan•3h ago•9 comments

Show HN: JSON Query

https://jsonquerylang.org/
75•wofo•3h ago•39 comments

Simplify Your Code: Functional Core, Imperative Shell

https://testing.googleblog.com/2025/10/simplify-your-code-functional-core.html
26•reqo•2d ago•5 comments

Creating an all-weather driver

https://waymo.com/blog/2025/10/creating-an-all-weather-driver
25•boulos•1h ago•8 comments

Avoid 2:00 and 3:00 am cron jobs (2013)

https://www.endpointdev.com/blog/2013/04/avoid-200-and-300-am-cron-jobs/
172•pera•3h ago•162 comments

Rust cross-platform GPUI components

https://github.com/longbridge/gpui-component
407•xvilka•10h ago•172 comments

Eight Million Copies of Moby-Dick (2014)

https://thevoltablog.wordpress.com/2014/01/27/nicolas-mugaveros-eight-million-copies-of-moby-dick...
21•awalias•4d ago•7 comments

Sieve (YC X25) is hiring engineers to build video datasets for frontier AI

https://www.sievedata.com/
1•mvoodarla•3h ago

Tags to make HTML work like you expect

https://blog.jim-nielsen.com/2025/dont-forget-these-html-tags/
337•FromTheArchives•10h ago•179 comments

A mild mannered Englishman who was the most prolific ghost hunter

https://lithub.com/the-mild-mannered-englishman-who-was-the-worlds-most-prolific-ghost-hunter/
10•tintinnabula•6d ago•1 comments

Solving regex crosswords with Z3

https://blog.nelhage.com/post/regex-crosswords-z3/
19•atilimcetin•6d ago•0 comments

Let the little guys in: A context sharing runtime for the personalised web

https://arjun.md/little-guys
44•louisbarclay•2h ago•5 comments

Show HN: Erdos – open-source, AI data science IDE

https://www.lotas.ai/erdos
33•jorgeoguerra•4h ago•16 comments

Why Nigeria accepted GMOs

https://www.asimov.press/p/nigeria-crops
24•surprisetalk•2h ago•44 comments

Show HN: Git Auto Commit (GAC) – LLM-powered Git commit command line tool

https://github.com/cellwebb/gac
22•merge-conflict•3h ago•22 comments

fnox, a secret manager that pairs well with mise

https://github.com/jdx/mise/discussions/6779
71•bpierre•3h ago•15 comments

Artificial Writing and Automated Detection [pdf]

https://www.nber.org/system/files/working_papers/w34223/w34223.pdf
26•mathattack•3h ago•14 comments

Gitworkshop.dev – Collaborate on code over Nostr

https://gitworkshop.dev/
10•sebastix•2d ago•0 comments

The last European train that travels by sea

https://www.bbc.com/travel/article/20251024-the-last-european-train-that-travels-by-sea
109•1659447091•11h ago•110 comments

Carl Bohland's Auto Wash Bowl (2015)

https://news.wttw.com/2015/07/29/ask-geoffrey
11•thunderbong•2h ago•5 comments

Should LLMs just treat text content as an image?

https://www.seangoedecke.com/text-tokens-as-image-tokens/
117•ingve•6d ago•76 comments

Fingerprint Formation (2004) [pdf]

https://math.arizona.edu/~anewell/publications/Fingerprint_Formation.pdf
6•o4c•2d ago•0 comments

It's insulting to read AI-generated blog posts

https://blog.pabloecortez.com/its-insulting-to-read-your-ai-generated-blog-post/
708•speckx•4h ago•352 comments

Corrosion

https://fly.io/blog/corrosion/
144•cgb_•4d ago•70 comments

Microsoft in court for allegedly misleading Australians over 365 subscriptions

https://www.accc.gov.au/media-release/microsoft-in-court-for-allegedly-misleading-millions-of-aus...
202•edwinjm•5h ago•86 comments