mirror of
https://github.com/ushahidi/SMSSync.git
synced 2026-04-25 07:45:53 +03:00
[GH-ISSUE #343] Confirm/clarify sent_timestamp placeholder being POST-ed #247
Labels
No labels
Bug report
Code improvement
Concern
Feature request
Feature request
Good first issue to work on
In progress
Needs info
Question
Ready
Translation
User Experience
User Experience
Website
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SMSSync#247
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
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?
@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.
@siddhartham-ysg commented on GitHub (Nov 5, 2015):
@eyedol thanks for clarifying!
@eyedol commented on GitHub (Nov 5, 2015):
@siddhartham-ysg 👍 Let me know if it's showing otherwise.
@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.