farktronix | 8 years ago | on: Show HN: Note Kitchen – Learn piano chords and scales
farktronix's comments
farktronix | 12 years ago | on: Bruce Schneier has changed his PGP key to 4096 bits
farktronix | 14 years ago | on: Poll: What database does your company use?
** The author disclaims copyright to this source code. In place of
** a legal notice, here is a blessing:
**
** May you do good and not evil.
** May you find forgiveness for yourself and forgive others.
** May you share freely, never taking more than you give.
(http://www.sqlite.org/src/artifact?name=a8571665d43ff18f89a4...)farktronix | 15 years ago | on: Color
farktronix | 15 years ago | on: IPv4 is depleted: Final five blocks allocated to registries
92 billion years is a long time to imagine. Let's say we won't have a use for these addresses after the sun dies in approximately 5 billion years, so we're going to try to use them all up by giving every person 1,000 /64 blocks.
Wolfram Alpha gives the surface area of earth as 5e18 square centimeters. 2^64 is approximately 1.8e19. With a single /64 block you could put two nanobots in every square centimeter on earth. That's not really practical over the oceans, but whatever.
With 1000 /64 blocks, you could cover the earth with nanobots that take up only 0.05mm^2 of space each.
Pixels on the average computer display take up 0.055mm^2.
You could address a display that covered the surface of the entire earth with just 1000 /64 blocks, and you could make one of these display for every person born until our sun dies.
It's an astoundingly huge number.
farktronix | 15 years ago | on: IPv4 is depleted: Final five blocks allocated to registries
The peak estimated birth rate on Earth was 173 million in the 1990s. If 200 million people were born every year and we gave every person a /64 block, we could allocate addresses for the next 92 billion years. The sun will be long dead by the time we use up that address space.
farktronix | 15 years ago | on: "Save a tree" with the WWF's new unprintable "green" PDF format
Dumping the strings on their binary turns up genRandStringLength:, so I'm guessing they're generating a string of random characters and setting that as the password on the PDF.
They're just shipping a modified version of Skim (http://skim-app.sourceforge.net) embedded inside their own app to do the PDF viewing.