If you are using my BlogCFC JS Twitter Pod or you visit my blog, you may have noticed that the Twitter time-stamp started reading "About 365 days ago" when the year rolled over. I finally sat down and looked into this today. Turns out, it's all my fault. I had to do some string manipulation on the date that Twitter sends to get it to work in IE and FF. Apparently I hard-coded '2007' in there to get it working. Maybe, I thought the world would end last year... Well, it didn't. So that code has been updated with #year(now())#.
The Twitter Pod download is still available here. And I'd still love to hear if anyone uses it on their blog.
In march I created a BlogCFC pod to show Twitter messages using the JS Twitter badge script. Recently, Twitter changed the location of the script.
So, my script
Also, Twitter's server seems to have load issues at times. This can pause pages to render slowly while they wait for the script file. So, if you move the script include to the bottom of tags/layout.cfm, then it won't interfere with the page rendering.
The download is still available here. And I'd still love to hear if anyone uses it on their blog.
I was looking at the Twitter Badges that you can add to your site. I noticed that there was a JS implementation. I thought that would be cool because I could style it to match the rest of the site.
So, I created a new empty BlogCFC pod and pasted in the code that Twitter offered. Well, I have to say I was very un-impressed. It basically is only set up to display the current message and the time it was added. Except there's even a typo. So, it wasn't even showing the date.
After a little investigation, I got it to show the date, which turns out to be the raw date, not the "about x [min|hours|days]" that I was expecting.
Well, I took that as a challenge and began to build out similar functionality to the Flash Twitter badge in my JS Twitter badge.