Danny Sullivan weighs in on URL shorteners, blasting ow.ly for its framed content that deprives the organization that created the content from page views and, thus, ad revenue. Top two: bit.ly and tr.im (I use both). New to me: cli.gs.
On Monday, Twitter reported that it is managing 50 million tweets a day (600 tweets per second). In 2007, the average (?) was 5,000 times a day and by 2009 hit 35 million a day.
Twitter Reports 50 Million Tweets Per Day
ComTweets (@comtweets) is a (free) service that organizes a Twitter community around a common email address, like Facebook organizes networks. The stated goal is to facilitate “easy discovery and communications between coworkers.” This is not unlikeYammer’s goal, but Yammer’s conversations are viewable only by people in the network (common email addresses). Of course, this means adding yet another social networking account to your plate.
The latest “celebrity death” to make the rounds on Twitter happened mid-day Thursday and was fueled by mainstream Canadian press. The “Drudge-ification” of North American news seems complete.
What’s more interesting than the Twitterstream is how the media treated their stories after the false report (AKA rumor) was outed.
[continue reading…]
Much has been made of Twitter’s role in helping raise money for victims of the Haitian earthquake. Less has been written about how Twitter makes it so easy to spread false information and the related need for digital literacy. I tackled these issues at several posts at WiredPen:
Prior to an interview on Friday about Twitter’s “staying power,” Caitlin Murphy (KIRO intern, UW grad) asked me that question. In preparation for our meeting, I tweeted: “Why do you like Twitter? Which is your favorite, Twitter or Facebook?”
I also looked at some of the answers to the question “What would you say to a friend who asked you about Twitter?” from our spring survey.
TweetDeck released version 0.32.0 today, a desktop application update that includes the new Twitter retweet feature. On the plus side, TweetDeck makes it easy to choose between sending an edited retweet and a new retweet. On the negative side, TweetDeck does not bump a tweet if you are already following a person who has been retweeted.
Almost two weeks ago, I urged early recipients of the Twitter retweet link to be cautious with its use, because most third party clients seemed unable to display these retweets.
Today I’m repeating the caution, and it’s not only because of spotty third party client implementation. It’s also because these new retweets don’t become “real time” in the Twitter.com timeline for tweets made by anyone you are already following.
For those of you who are in the Twitter “retweet” beta test, I have a word of advice: proceed cautiously.
Here’s why. Currently, retweets that are executed via the Twitter web “retweet link” are visible to your followers who are using theweb interface to read your tweets but are not visible to popular third party clients.
Not at the OK Corral but at the Web 2.0 Summit. Microsoft and Bing face off against Google; the fight is over Twitter, as Microsoft has Facebook in its pocket. (Remember the $240 million investment.) Marshall Kirkpatrick at ReadWriteWeb sorts through the search fight that came to a head today.
Most Facebook users want “privacy” (there’s the reciprocity thing) and keep their content protected. Most Twitter users want connections and keep their content public (ie, not protected). I think it will be more difficult to convince Facebook folks to “open up” than Twitter folks to update their Google profiles, if by updating the profile they’ll get better (more contextual, more meaningful) search results.