Feb
23
This morning, a new version of BeTwittered went live. Because it’s web based the update is automatic, so if you already use BeTwittered, you’ll just get the updates. For most people, the obvious change will be the addition of time-stamps. If you don’t like having them, you can turn them off in the “settings” - FYI - Pictures can be turned off, too. Now, someone (I won’t mention a name, but it rhymes with “Steve”) noted that at some screen resolutions, BeTwittered didn’t “wrap” well, so made it hard to read Tweets without having to scroll around the screen. I checked it out, and it was truly a pain, and ugly. I’ve fixed the text area so it resizes, so BeTwittered should now look a LOT better for anyone that had this issue before. Happy Tweeting.
Comments
3 Responses to “BeTwittered gets a new feature, and some nice changes”
Leave a Reply
[...] I got a bit of a lesson this morning. I updated BeTwittered, and was very pleased. Well, until I noticed that the formatting was junk. What did I learn? Stylesheets get cached, and pretty liberally. So if you were using BeTwittered this morning, and it suddenly looked a bit clunky, my apologies. One interesting thing, IE was better than Firefox in this case. It surprised me that IE picked up the changes when I closed it and re-opened. Firefox was VERY stubborn… So, here’s the “official” notice. [...]
When twitxr updates are posted to twitter it messes up the url by separating the last two characters for some reason….an example tweet below.
vkoser: The aforementioned new floor - photo at http://twitxr.com/vkoser/updates/73 80
for instance where the url should end in 7380. Checking the api feed at http://twitter.com/statuses/friends_timeline.xml the url is correct and the tweet is non truncated.
Just thought I’d let you know, thanks for the great widget.
Thanks for the feedback! I’ll have a look tonight. I think I already know what the problem is. This should be a pretty quick fix. I have a bit of code that is supposed to make sure long words wrap nicely. It’s probably just “eating” long links for lunch. I’d probably only done testing with “tinyurl” links, which tend to be very short. Not sure how it went this long without me noticing it myself.
Thanks Vince!