This morning you can almost hear the noise of thousands of Jaiku friendship invitations arriving in all our mailboxes: with the acquisition news everybody is back checking Jaiku.
I like the "aggregator" approach of Jaiku, I'm wondering what would happen if they would go all the way and, for example, really become a full Twitter client.
Today Jaiku only collects twitter posts from Jaiku users who configured their accounts accordingly, but there's no technical reason why Jaiku could not collect for me posts from all my Twitter friends (well, a reason might have been server load, which won't be an issue anymore with Google resources), not only the one subscribed to both services. And, of course, there's no reason why Jaiku could not forward whatever I post on their service to my Twitter account, maybe scaling it down gracefully when needed (i.e.: shortening urls, scaling down images, converting links to their mobile version where applicable).
If Jaiku would do these moves, there would be no reason for me to ever visit Twitter again: I would get all Twitter content simply visiting my Jaiku account, plus all the other information that Jaiku is collecting for me.
I think that once fully interoperable, we will see the separation of the transport layer (how messages are relayed to whom) from the actual services layer. At this point the two are very close, actually you can only send short burst of text on Twitter, but as/if these services will evolve (just look at everything Dave is doing with Twitter every day to have an idea), the real deal will be with the added value things you'll be able to do with these network, not which backbone you are using to move them around.
Technorati Tags: Jaiku, twitter
comments: |
View blog reactions
