lucky-commit

they're not Particularly Rare, But I think they're more pleasing to See. For instance This "2822302" Makes me Especially Happy: https://github.com/BrowserBox/BrowserBox/commit/2822302387c4cb7ff71c4239da3dc5fa4c… It Even Extends up to 10 digits! That's Not Particularly rare - Roughly 1% chance (10^10/16^10 i think) - But i just think they look nice. Are there any other people out there who are particularly pleased when they hit that? sorta like hitting 7777 on the odometer, or whatever. I'm also a fan of the purely Numeric Identifiers Twitter/X Uses (and has for ages). This all reminds Me of That "commit Fuzzing tool" That Can Make Your log have whatever Commit You Want. asked AI, turns out it's: https://github.com/not-an-aardvark/lucky-commit Lucky Commit! what a perfect name. i guess this ask hN should be: does anyone else like luck

https://github.com/not-an-aardvark/lucky-commit and others have shown up to engineer (read: brute-force) these early hash digits

Selective partial SHA1/SHA2 matches only take a few seconds. https://github.com/not-an-aardvark/lucky-commit

From the same author: https://github.com/not-an-aardvark/lucky-commit a tool for generating commits with specific shorthashes.

You can do a lot with various whitespace characters, see for example https://github.com/not-an-aardvark/lucky-commit.

See also Lucky Commit [0], which uses various types of whitespace characters instead of a hash inside the commit, which makes it look more magical. I wonder about performance, though. Why is the author's method slower than the package I linked? [0]: https://github.com/not-an-aardvark/lucky-commit

Hah, that's clever. The author is using their other toy research tool/project: https://github.com/not-an-aardvark/lucky-commit