Hacker News new | past | comments | ask | show | jobs | submit login

> Obviously we need to add the date the coordinates were encoded. The decoding will have to apply correction based on ample databases of tectonic data. A simple formula will not work, a major earthquake can move a rift by some 5-10 cm. And you need to know exactly what plate does the coordinate refer to, is not as simple as 'Australia moves 7cm a year', consider parts of California east vs. west of the fault. Well, that spiraled out of control fast... It makes the time issues like [0] seem trivial by comparison.

I didn't think it was possible to come up with an idea worse than leap seconds but we did it guys!




> I didn't think it was possible to come up with an idea worse than leap seconds but we did it guys!

Leap seconds aren't the problem, its the fact that we're stuck on a Babylonian style of timekeeping. Measuring time with completely uncorrelated rotations of objects is a ... fun idea. Or maybe the problem is that time is very hard to determine "naturally".


Time is very easy to define naturally as long as it's always "local." Local noon is when the sun is at its highest. Local midnight is halfway between noons, come up with some subdivision, and you're done.

It breaks down once you need to synchronize distant events of course...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: