Twitter killed the API v1 twitter-panel script about eight weeks ago. The decision was about as popular as one might expect. This is the script I used on almost every single client’s site. I used it because it was awesome.
With the API v1.0 script, I could style every single element of the panel. I could make each tweet dance in its own box or bubble. I could give alternating tweets different colors. The fonts could match the fonts of the page. I could knock out the background. I could dispense with the border entirely. I had absolute control over my scrollbar. I could set my own width, as small or as big as I wanted. Anything was possible and I did a lot of awesome things with my twitter panel.
Then, eight weeks ago, Twitter deprecated API v1.0 andÂ rolled out the API v1.1 as a replacement.
With API v1.1, instead of an elegantly styled twitter feed on my sites, I can place a big brick-of-a-box that is IMPERVIOUS to styling.
I was hoping the Facebook panel would start to go in the direction of styling freedom like the Twitter panel. Instead, Twitter devs have followed in the anti-designer footsteps of Facebook developers, opting to put me in the same straightjacket Facebook wants me in.
Twitter devs: You took away a tool I used daily to make websites better, your replacement sucks balls, and I am extremely unhappy. I was hoping by now you would have realized how incredibly bad this decision was – from a designer’s perspective – and listened to all the CSS coders who have been screaming about this decision. I’ve been holding off criticism of API v1.1, but this morning I’ve had the following conversation for I think the tenth time:
“Yes, I am aware your twitter stream isn’t there anymore. I’m sorry, I had to remove it.”
“Well, you see, Twitter made the old twitter panel not work anymore, and the new twitter panel could not be styled to match your page like the old twitter panel could. For example, the little icons cannot be made invisible, the background is either dark grey or white I’m afraid, the fonts won’t match, etc. etc. It’s basically a big ugly brick. The whole thing had to go. I had to remove it. Again, I’m sorry.”
“No, like I said, the new twitter widget cannot be styled. That means it will stand out like a sore thumb in the sidebar. We won’t be able to make it display the way it used to. The new panel was a detriment to the site, so it had to go.”
“No, I’m sorry, I do not actually know why they did this.”
“Yes, I’ve been having this conversation with all of my other clients as well.”
“No, I don’t believe they would be willing to reimburse you for the development costs to style the twitter panel. I’m afraid that money is in the toilet.”
I’m really tired of this conversation. I resent you, twitter devs, for putting me in this position. A pox on you all.