[GH-ISSUE #343] Confirm/clarify sent_timestamp placeholder being POST-ed #247

Closed
opened 2026-02-28 01:23:51 +03:00 by kerem · 4 comments
Owner

Originally created by @siddhartham-ysg on GitHub (Oct 29, 2015).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/343

The developer docs say this about sent_timestamp:

sent_timestamp -- the timestamp the SMS was sent. In the UNIX timestamp format

What was expected is that: that this is the unix time-stamp when the SMS was received, however as it happens to be the time-stamp is when the SMS is being relayed to or POST-ed to an URL/I for the application I am building?

What should be the expected/appropriate behaviour? Is what i am facing appropriate behaviour?

Originally created by @siddhartham-ysg on GitHub (Oct 29, 2015). Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/343 The developer docs say this about _sent_timestamp_: > sent_timestamp -- the timestamp the SMS was sent. In the UNIX timestamp format What was expected is that: that this is the unix time-stamp when the SMS was received, however as it happens to be the time-stamp is when the SMS is being relayed to or POST-ed to an URL/I for the application I am building? What should be the expected/appropriate behaviour? Is what i am facing appropriate behaviour?
kerem 2026-02-28 01:23:51 +03:00
  • closed this issue
  • added the
    Question
    label
Author
Owner

@eyedol commented on GitHub (Nov 5, 2015):

@siddhartham-ysg It's the timestamp when the SMS was sent to the phone. In other words when it was received. The timestamp is not when it was posted to the server.

<!-- gh-comment-id:153914281 --> @eyedol commented on GitHub (Nov 5, 2015): @siddhartham-ysg It's the timestamp when the SMS was sent to the phone. In other words when it was received. The timestamp is not when it was posted to the server.
Author
Owner

@siddhartham-ysg commented on GitHub (Nov 5, 2015):

@eyedol thanks for clarifying!

<!-- gh-comment-id:153977830 --> @siddhartham-ysg commented on GitHub (Nov 5, 2015): @eyedol thanks for clarifying!
Author
Owner

@eyedol commented on GitHub (Nov 5, 2015):

@siddhartham-ysg 👍 Let me know if it's showing otherwise.

<!-- gh-comment-id:153981329 --> @eyedol commented on GitHub (Nov 5, 2015): @siddhartham-ysg :+1: Let me know if it's showing otherwise.
Author
Owner

@siddhartham-ysg commented on GitHub (Nov 5, 2015):

@eyedol In the past few weeks certain circumstances we were inclined to infer this, it could really be an observational anomaly; today we checked the behaviour again and it worked out as you have mentioned.

<!-- gh-comment-id:153992122 --> @siddhartham-ysg commented on GitHub (Nov 5, 2015): @eyedol In the past few weeks certain circumstances we were inclined to infer this, it could really be an observational anomaly; today we checked the behaviour again and it worked out as you have mentioned.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/SMSSync#247
No description provided.