created_at time can be out of order in relation to status_id

0 views
Skip to first unread message

tweetip

unread,
Aug 9, 2008, 2:54:49 AM8/9/08
to Twitter Development Talk
The time extracted from created_at can be more than 1 minute off
within tweets ordered by status_id.

Alex, should I create an issue report?

871799064 14:42:32 thevixy earthquake
871799216 14:42:42 thevixy earth quake
871799348 14:42:50 gamingangel holy crap earthquake!~
871799431 14:41:32 victuoso EARTHQUAKE!!
871799473 14:41:41 Brad Earthquake!!!!!!!!!!!!!!!! It's still
shaking!
871799583 14:42:58 brendoman still going
871799592 14:42:59 ischafer Century City Earthquake just
happened. Still going
871799604 14:43:01 nicefishfilms Earthquake in Dana Point- still
feeling it!
871799606 14:43:01 chygga EARTHQUAKEEEEEEEEEEEEEEEEEEEEEEEEE

tweetip

unread,
Aug 9, 2008, 5:15:06 PM8/9/08
to Twitter Development Talk
Some may be interested in the confusion created by a bad timestamp -
it certainly had me second guessing even my own internal data. I've
updated a screenshot of what we observed that morning here http://tweetip.us/lkr1g

14:42:29 14:42:32 thevixy earthquake
15:04:06 15:04:06 tweetip Earthquake S California ~ 1st tweet...
http://tweetip.us/lkv1a
15:13:30 15:13:30 biz Wow, the first person who reported the LA
earthquake on Twitter was @nckhwks at 11:41:14 AM PST http://bit.ly/3WJCx2
15:13:36 15:13:36 tweetip Earthquake S California ~ Timeline graph
of 1st tweets... http://tweetip.us/lkutx
15:15:18 15:14:16 andygadiel @biz strange, usgs says earthquake
occurred at 11:42:15 AM, need to get Twitter in sync with them, or
visa versa.
15:18:07 15:18:08 jack First Twitter update about the earthquake:
http://twitter.com/nckhwks/statuses/871799161
15:18:35 15:18:35 maslowbeer @biz wow! he foresaw the earthquake by
a full minute! maybe he caused it? ;)
15:21:41 15:19:18 jack Actually, it may be this one!
http://twitter.com/thevixy/statuses/871799064

Reply all
Reply to author
Forward
0 new messages