Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The Stack Exchange API, version 1.1, documentation is ever so slightly confusing wherever Unix timestamps are mentioned (perhaps any ranges, I haven't dug too deeply)

For instance:

todate – Unix timestamp of the maximum creation date on a returned item.
unix epoch date, range [0, 253,402,300,799]

It took me a very brief moment to understand what was intended by the italicized part. For clarity, perhaps this should be edited to one of the following:

...unix epoch date, range [0, 253402300799]

...unix epoch date, range [0 .. 253,402,300,799]

...unix epoch date, range [0 - 253,402,300,799]

share|improve this question

migrated from Jul 17 '13 at 13:31

This question came from our discussion, support, and feature requests site for professional and enthusiast programmers.

Whoopsy doodle; didn't know it was a Stack Apps question. Thanks for the migrate :-) – Northborn Design Jul 17 '13 at 13:34
Hm, I don't know how likely it is that the legacy API documentation will be fixed. I don't believe that the 2.x documentation exhibits the same error, but I haven't read through it comprehensively. – Tim Stone Jul 17 '13 at 13:43
@TimStone Spot on; didn't see it was fixed there. Well, I'll leave this here for the sake of completeness, but you're right. – Northborn Design Jul 17 '13 at 13:45
Wish I knew why a simple retag turns into a full-blown suggested edit! (Note that once that happened, I went ahead and made a couple minor edits to clarify the Q.) – Brock Adams Jul 17 '13 at 14:22
@BrockAdams All good; thanks :-) – Northborn Design Jul 17 '13 at 14:23

You must log in to answer this question.

Browse other questions tagged .