News for hackers. Stuff that matters.
Re:Note the commit hash by rspeer on Sunday April 06, 2014 @06:16PM (#7543351)
It is almost certain that there are a quarter-billion published Git commits by now. (GitHub says there were 150 million pushes in 2013 alone, and many of those have multiple commits.)

This means it is likely that, purely by coincidence, someone has at some point had their commit labeled as (badc0de).

Re:Note the commit hash by gwern on Sunday April 06, 2014 @06:24PM (#7543399)
Github doesn't seem to allow searching revision hashes, but presumably Google has most of Github crawled by now, and I didn't spot any commits with that as a label: https://encrypted.google.com/search?num=100&q=badc0de%20site... (more hits than I expected though).
Re:Note the commit hash by tlrobinson on Sunday April 06, 2014 @06:32PM (#7543450)
Google doesn't appear to match partial hashes. I searched for a random GitHub commit hash, and it showed up, then removed one character, and it didn't.
Re:Note the commit hash by maxerickson on Sunday April 06, 2014 @06:40PM (#7543499)
If you switch to verbatim there are only about a dozen.

I think the odds of an accidental collision with badc0de are pretty low.

Re:Note the commit hash by sexmonad on Sunday April 06, 2014 @06:44PM (#7543512)
Each hex character represents 4 bits. That means that a 7 character string is 28 bits. That's about 268 million possibilities. On average, it would take around 134 million commits to get one that started with "badc0de".
Re:Note the commit hash by Strilanc on Sunday April 06, 2014 @10:04PM (#7544249)
Interesting

    1 - (1 - 1/16^7)^250000000 ~= 61%