Now this tool lets you combine peoples conversations on Twitter in one time line. Pretty cool. So I can now just enter a few peoples names or id's and I can see the whole conversation I caught the tail end of.
How does this fit with the title? Well, more and more I'm seeing Twitter being absorbed into or used by other tools/applications. Most Web2.0 social sites let you post to or display from Twitter. Other people are building tools to show the mood, locale, to search and monitor, and general pull or push whatever they can through the API.
So is that what Titter should resolve itself to be - Just an API to hang communication on? Maybe that could be it's business model. How many people are actually logging in to the Twitter website as opposed to using it through something like HelloTxt or their phone, Snitter, Flock or Twhirl.
As netizens shift from shiny object to shiny object I believe Twitter will still be there. I just don't think we'll be as aware of it's presence as we are now. It'll just be that thing we use to communicate.
Technorati tags: twitter, api, future
Blogged with the Flock Browser
5 comments:
A quick glance at my Twitter front page reveals that folks are using text messaging and Pageflakes to post tweets this morning. I'm not the only one who still uses the web interface, but we do seem to be in the minority.
I think you bring up some good points. People have taken the API and done some really cool things with it.
I still use the web version for several reasons:
- I don't like it constantly interrupting like an IM
- I don't want it sent to my devices
- I don't use it on my devices (except to read)
I tend to use a command line Twitter tool, that shows me all tweets since last time I read - allowing me to keep in the loop.
So, other than occasionally using the command line, I refer back to the website.
What do you think about this, in light of the password anti-pattern, as there is no other way to authenticate the Twitter API besides giving them your username and password.
@kris - That is a good thing about their homepage and part of the reason for the post. They let you see where tweets are coming from.
@nate - Twitter is an offender on the whole password anti-pattern but they do have an OAuth API though apparently this is still lacking. Here's hoping they switch soon.
@David
The problem is that they don't have an oAuth in place right now. I have used their API for a few personal projects, and there is nothing public related anything other than standard HTTP Authentication.
"For the time being, HTTP Basic Authentication is the only supported authentication scheme."
[via: http://apiwiki.twitter.com/REST+API+Documentation]
It's for this reason that I stick to the homepage to check my tweets, and not hand out my username/password to the newest shiny twitter tool. I would agree that many of the mashups are very cool, and fill a void where twitter itself lacks - I just don't like the implementation.
it seems like twitter is being web troika'd
Post a Comment