{"action":"created","issue":{"url":"https://api.github.com/repos/nlopes/slack/issues/55","repository_url":"https://api.github.com/repos/nlopes/slack","labels_url":"https://api.github.com/repos/nlopes/slack/issues/55/labels{/name}","comments_url":"https://api.github.com/repos/nlopes/slack/issues/55/comments","events_url":"https://api.github.com/repos/nlopes/slack/issues/55/events","html_url":"https://github.com/nlopes/slack/pull/55","id":130052377,"number":55,"title":"Remove JSONTimeString","user":{"login":"dvdplm","id":18515,"avatar_url":"https://avatars.githubusercontent.com/u/18515?v=3","gravatar_id":"","url":"https://api.github.com/users/dvdplm","html_url":"https://github.com/dvdplm","followers_url":"https://api.github.com/users/dvdplm/followers","following_url":"https://api.github.com/users/dvdplm/following{/other_user}","gists_url":"https://api.github.com/users/dvdplm/gists{/gist_id}","starred_url":"https://api.github.com/users/dvdplm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dvdplm/subscriptions","organizations_url":"https://api.github.com/users/dvdplm/orgs","repos_url":"https://api.github.com/users/dvdplm/repos","events_url":"https://api.github.com/users/dvdplm/events{/privacy}","received_events_url":"https://api.github.com/users/dvdplm/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-01-30T23:28:32Z","updated_at":"2016-03-05T14:03:44Z","closed_at":"2016-03-05T14:02:53Z","pull_request":{"url":"https://api.github.com/repos/nlopes/slack/pulls/55","html_url":"https://github.com/nlopes/slack/pull/55","diff_url":"https://github.com/nlopes/slack/pull/55.diff","patch_url":"https://github.com/nlopes/slack/pull/55.patch"},"body":"The Slack API docs explicitly states that their funny timestamps are to be treated as a sort of message IDs and are guaranteed to be unique in the channel. In update and delete calls it is necessary to know the timestamp-string or the call will fail. Client code will use these timestamp-strings for things like checking for duplicate messages.\r\n\r\nInstead of casting incoming timestamp-strings to (english speaking) human-readable strings like \"Sun Jan 31\" I think it's wise to let the client do its own formatting and leave the timestamp-strings be.\r\n\r\n[Slack docs](https://api.slack.com/rtm):\r\n\r\n```\r\nAll messages within a single channel are guaranteed to have a unique timestamp which is \r\nASCII sortable. Given the precision of the timestamp, clients should treat these timestamps \r\nas strings, not floats/doubles.\r\n```"},"comment":{"url":"https://api.github.com/repos/nlopes/slack/issues/comments/192650816","html_url":"https://github.com/nlopes/slack/pull/55#issuecomment-192650816","issue_url":"https://api.github.com/repos/nlopes/slack/issues/55","id":192650816,"user":{"login":"nlopes","id":652790,"avatar_url":"https://avatars.githubusercontent.com/u/652790?v=3","gravatar_id":"","url":"https://api.github.com/users/nlopes","html_url":"https://github.com/nlopes","followers_url":"https://api.github.com/users/nlopes/followers","following_url":"https://api.github.com/users/nlopes/following{/other_user}","gists_url":"https://api.github.com/users/nlopes/gists{/gist_id}","starred_url":"https://api.github.com/users/nlopes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nlopes/subscriptions","organizations_url":"https://api.github.com/users/nlopes/orgs","repos_url":"https://api.github.com/users/nlopes/repos","events_url":"https://api.github.com/users/nlopes/events{/privacy}","received_events_url":"https://api.github.com/users/nlopes/received_events","type":"User","site_admin":false},"created_at":"2016-03-05T14:03:44Z","updated_at":"2016-03-05T14:03:44Z","body":"Thank you!"}}