Closed fpjr closed 9 years ago
ts is an identifier and it's unique per channel. The part before the dot is a Unix timestamp and the part after the dot is used to keep the message order.
On Sun, Jul 19, 2015 at 1:22 PM, fredpedro notifications@github.com wrote:
I wonder how the 'ts'(timestamp) of each messages in a chat.history method is being read, or is humanly readable.
Reply to this email directly or view it on GitHub: https://github.com/slackhq/slack-api-docs/issues/31
Thank you!, makes much sense now.
Thanks for jumping in to help, Ernesto! We'll be continuing to monitor issues here, but for a faster reply time in future, you can also contact us with any questions or issues using feedback@slack.com.
I wonder how the 'ts'(timestamp) of each messages in a chat.history method is being read, or is humanly readable.