I can see why you'd want this: the timestamp of the tweet is relative to the time of the server, if the client's local-time is not perfectly in-sync the current messages would appear to either be in the past or future. Especially useful when using the streaming API.
↧