This Is What Twitter Does Not Want To Happen, Part Seven

New Twitter Has Become Browser Poison is, at the time of this post, the most-read post at this blog.

A search term that led to this blog today:

“new twitter” firefox cpu 100% 2011

Yep. Twitter is browser poison again:

http://twitter.com/#!/mikecane/status/90896766702059520

http://twitter.com/#!/mikecane/status/91558135696867328

I did get a reply — that I cannot find, due to rotten Twitter Search (which, by the way, would give me only the past day of tweets, so I had to use Topsy) — acknowledging they know of this issue.

It was fixed once before.

But what made it happen again?

Twitter can’t afford to drive people away from its website.

With all the talk of Google+, people are bound to try it. Some might decide to switch just because using Twitter in their browser has become a painful experience, with it now nearly hijacking their computer.

If Twitter has a strategy to encourage people to use clients, instead of its website, it should be explicitly stated.

Previously here:

This Is What Twitter Does Not Want To Happen
This Is What Twitter Does Not Want To Happen, Part Two
This Is What Twitter Does Not Want To Happen, Part Three
This Is What Twitter Does Not Want To Happen, Part Four
This Is What Twitter Does Not Want To Happen, Part Five
This Is What Twitter Does Not Want To Happen, Part Six

6 Comments

Filed under Socialtech

6 responses to “This Is What Twitter Does Not Want To Happen, Part Seven

  1. I’ve tweeted thousands of times, but I doubt I’ve used Twitter.com to do this more than a few dozen times. Have always used a client. The Twitter app for Mac is lightweight, fast, and unobtrusive on my desktop. So much better than TweetDeck.

    I do use TweetDeck to manage lists, however, because the Twitter interface is so ridiculously opaque for this and other things. BTW, the only reason I do go to Twitter is to edit my profile, etc. But never to tweet.

  2. Oh, maybe that’s why I’ve had to restart my browser so often over the past few days! Getting used to seeing that spinning pinwheel daily… I’d forgotten about that since the last time this was fixed. Do you know when it started again?

    • mikecane

      You get a pinwheel? I get massive amounts of HD thrashing. Something to do with their JScript schemes, I suppose. They know it’s cloggy again, so we have to let them fix it. They did once, even though it took near two months, I think!

      • Yep. That’s what you get on a Mac when the application is unresponsive: the dreaded spinning pinwheel. In this case, it’s the browser doing it more often. I must close Twitter now that Echofon is working again (more or less) and see if it continues.

      • mikecane

        Wow. All that Mac horsepower being drained away by Twitter!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s