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
Might be a side effect of using a modern floating point decimalization algorithm like Grisu3, which minimizes the number of significant digits necessary to uniquely represent the floating-point value
Nah, they actually have an ad-hoc spec that is quite a mess: https://tc39.github.io/ecma262/#sec-tostring-applied-to-the-number-type … There's a Python module 'frepr' that uses the V8 JS engine impl and yet it *doesn't* do this, which makes me think the actual JS engine has horrible special cases to meet the crazy JS spec.
Honestly, it's weird. V8 is supposed to use Grisu (also FF), which is supposed to be what became the double-conversion library, which frepr uses, and yet the crazy result in Chrome/FF is different from that (but matches the ECMAScript spec).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
