I like to install as few things on my PC as possible. That's why when TweetDeck released an app for Google Chrome in Dec. 2010, it was an epiphany.
No need to run another program in the background. Simply flick open a new browser tab and bam: Your Twitter columns are there in all their HTML5 glory.
Then, in May 2011, Twitter acquired TweetDeck. "That's cool," we thought. "Who better to manage a Twitter app than Twitter itself?"
For a while, things were fine. Small tweaks and improvements were welcome surprises.
Then, New Twitter emerged, and with it, a brand new version of "ChromeDeck." Cosmetically, it's got a bit more snazz. But the more I use it, the more I find it lacking under the hood. Existing features I had grown to rely on in the previous version are nowhere to be found.
Why, Twitter? Why?
The first thing you'll notice on firing up the new ChromeDeck is a huge swath of dead space on the right. If every single pixel of your right-most column doesn't fit on the screen, it's bumped to the next page.
While the new "page" navigation is handy, this empty real estate is odd and disappointing.
I'll never understand Twitter's war on the "RT" convention, a tidbit devised by the network's early community and still used today. Many third-party apps have the option baked in, but nearly all of Twitter's own interfaces (from the .com to the mobile apps) have never included it.
ChromeDeck used to have a simple two-click retweet mechanism. One click to retweet internally, a second click to modify it using RT.
The new version has abandoned this in favor of quotation marks, a vile solution that was never part of Twitter's semantic zeitgeist.
One of the best features of TweetDeck for Chrome was the ability to right-click on a page in your browser and share it directly to Twitter.
TweetDeck would pull in the title of the page, automatically shorten the link and allow you to edit the tweet before sending.
This wonderful, time-saving feature was clearly too awesome for the new version.
Drop any link into your 140-character composition and TweetDeck used to automatically shorten it with a j.mp wrapper (an alias for bit.ly).
Not so in the new version. By default, links are pushed directly through Twitter, which will abbreviate them if necessary with ugly ellipses.
You can connect your own bit.ly account to TweetDeck using an API key, but even still, links don't shorten before you hit "send" the way they once did.
The new ChromeDeck has the option to display Twitter handles or full names in your feeds. Great.
However, it's inconsistent when displaying retweets, as in the picture here. Thus, confusion.
Why?
The first thing you'll notice on firing up the new ChromeDeck is a huge swath of dead space on the right. If every single pixel of your right-most column doesn't fit on the screen, it's bumped to the next page.
While the new "page" navigation is handy, this empty real estate is odd and disappointing.
I'll never understand Twitter's war on the "RT" convention, a tidbit devised by the network's early community and still used today. Many third-party apps have the option baked in, but nearly all of Twitter's own interfaces (from the .com to the mobile apps) have never included it.
ChromeDeck used to have a simple two-click retweet mechanism. One click to retweet internally, a second click to modify it using RT.
The new version has abandoned this in favor of quotation marks, a vile solution that was never part of Twitter's semantic zeitgeist.
One of the best features of TweetDeck for Chrome was the ability to right-click on a page in your browser and share it directly to Twitter.
TweetDeck would pull in the title of the page, automatically shorten the link and allow you to edit the tweet before sending.
This wonderful, time-saving feature was clearly too awesome for the new version.
Drop any link into your 140-character composition and TweetDeck used to automatically shorten it with a j.mp wrapper (an alias for bit.ly).
Not so in the new version. By default, links are pushed directly through Twitter, which will abbreviate them if necessary with ugly ellipses.
You can connect your own bit.ly account to TweetDeck using an API key, but even still, links don't shorten before you hit "send" the way they once did.
The new ChromeDeck has the option to display Twitter handles or full names in your feeds. Great.
However, it's inconsistent when displaying retweets, as in the picture here. Thus, confusion.
Why?
No hay comentarios:
Publicar un comentario