You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I'm not sure what number you're talking about. It's JS that is printing impossible numbers. 4611686018427387904 *is* possible to represent in float64. *Exactly*. With zero loss of precision. Absolutely, 100% exactly that number.
4611686018427388000 is *not* possible to represent in float64. It does not exist on the set of possible float64 values. And yet, when you take 4611686018427387904, represent it as a float64 (which JS can do), and toString() it, JS returns 4611686018427388000 which is *wrong*!
4611686018427387904 (decimal) == 2^62 == 0x1.0000000000000p+62 (float64) == [43 d0 00 00 00 00 00 00] (big-endian hex encoding of float64) are all representations of the same, exact, precise integer, with no loss or rounding. But JS's toString returns 4611686018427388000.
Literally, the bytes inside a JS interpreter's RAM will contain [43 d0 00 00 00 00 00 00], per the IEEE 754 spec that *means 4611686018427387904*, and yet you call toString on that value and it returns something else. I don't know how to make this any clearer.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
