Skip to content
This repository has been archived by the owner on Mar 10, 2018. It is now read-only.

Timestamp discrepancy #29

Open
outhouse opened this issue Feb 9, 2014 · 3 comments
Open

Timestamp discrepancy #29

outhouse opened this issue Feb 9, 2014 · 3 comments

Comments

@outhouse
Copy link

outhouse commented Feb 9, 2014

I've noticed a discrepancy between timestamps for tweets fetched through this plugin / getmytweets api.

Example -

Original Tweet: 06/02/2014 12:33 AM
https://twitter.com/umutm/status/431344872877228032

Same tweet as displayed through Tweetable : 06/01/2014, 08:49
http://jsfiddle.net/Rur72/

@philipbeel
Copy link
Owner

I will look into this.

@outhouse
Copy link
Author

outhouse commented Feb 9, 2014

awesome, thanks

@dracnet
Copy link

dracnet commented Apr 7, 2014

solved. change

tweetMonthInt = n++;
by
tweetMonthInt = n+1;

full code:
for(n=0; n<12; n++) {
if(shortMonths[n] === tweet.tweet_date.substr(4, 3)) {
tweetMonthInt = n+1;
tweetMonth = (tweetMonthInt <= 9) ? '0' + tweetMonthInt : tweetMonthInt ;
break;
}
}

DanielMcAssey added a commit to DanielMcAssey/Tweetable that referenced this issue Apr 26, 2014
This commit fixes issue philipbeel#31 with reference to caching and fixes issue
philipbeel#29 to fix the timestamp.
I have also included a minified version.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants