"created_at" misbehaves


when using the rest 1.1 direct_messages.json call i usually recieve the correct time but on some issues i get diffects with the time
anything i should know of other than the “created_at” attribute in the message json to get the correct utc time?


solved;) apparently there was a temp issue with the twitter site itself which presented the message on the 23th Nov while it was on the 24th.


Thanks for confirming this is resolved now!

closed #4