Project trying to compute BB(5) once and for all. Notably it has better presentation and organization than any other previous effort, and appears to have grouped everyone who cares about the topic as of the early 2020s.
Very cool initiative!
By 2023, they had basically decided every machine: discuss.bbchallenge.org/t/the-30-to-34-ctl-holdouts-from-bb-5/141
This notation is cool as it gives the spin quantum number, which is important e.g. when talking about hyperfine structure.
But it is a bit crap that the spin is not given simply as but rather mixes up both the azimuthal quantum number and spin. What is the reason?
Minimal example: nodejs/sequelize/raw/recursive.js
More advanced SQL tree traversal examples: nodejs/sequelize/raw/tree.js
Cool data embedded in the Bitcoin blockchain IRC log dumps Updated 2025-06-17 +Created 1970-01-01
tx 210000d1392bec2505d1289e5c39c2039204ff1ecf7eef55f973ccd3111003e1, block 360235 (2015-06-10) and the following transactions have transcripts of a very long developer chat starting with:
TODO purpose? The transcripts are interspersed with developers likely voting for project leadership, and commenting on Gavin.
TODO find original discussion location, these are almost certainly from one of the Bitcoin IRC channels.
Part of the goal of this dump is that the Bitcoin developers have a policy of not allowing logging on their talk channel, and this released it all to the blockchain forever where it cannot be deleted. These might just be more of protests against larger block sizes.
There are unlisted articles, also show them or only show them.