Twitter for Android

[Muthu Ramadoss]

Team,

Here's my simple idea:

1. Run your own Jabber server.
2. Let all the Android mobiles publish to your Jabber server.
3. Broadcast the messages from your Jabber server to the Android
mobile subscribers.

This is more or less like Twitter for Android. Android uses GTalk to
communicate between mobiles. Can you all suggest me how to go about
this? I'm in particular interested in what kind of protocol to use,
between Android mobiles and to and fro from mobiles to server.

Thanks.

[friedger]

Why isn't Gtalk enough for now?
Friedger

[Muthu Ramadoss]

Friedger,

Good question. Take the instance of Twitter.. If Twitter uses GTalk, can
it provide services like public_timeline, friends_timeline, follow,
leave etc., So if we need control of the data, I'm not sure if GTalk can
provide that. I don't have any prior experience with IM, Jabber, XMPP
etc., So I'm still learning.

What do you think?

--
Thanks.

Muthu Ramadoss
http://www.intellibitz.com
http://groups.google.com/group/android-chennai
http://www.slideshare.net/intellibitz
+91 44 22476750

We develop open source solutions for mobile handsets, using Android.

[Peli]

I just looked at the twitter API homepage:
* http://groups.google.com/group/twitter-development-talk/web/api-documentation

It seems currently they mainly support HTTP requests with basic HTTP
authentication.
Replies come in the form of XML, JSON, RSS, or Atom (as one requests).

HTTP + XML should not be too difficult... an OpenIntents wrapper
around this would indeed be cool :-)

Note that requests are limited to 1 per minute (which should be enough
for most). If you want to go beyond, you have to use XMPP, but they
don't publicly give the specifications for that.

Peli

> Muthu Ramadosshttp://www.intellibitz.comhttp://groups.google.com/group/android-chennaihttp://www.slideshare.net/intellibitz

[Zero]

i would say, because gtalk is a locked in system.
and if i read it right, google plans to move gtalk to a
closed source protocoll.
i dont wanne see phone-to-phone communication
locked to a single service provider. it should be an open system
not only for android and not only for google users.
xmpp does just that. and it's capable of more than just im.

what realy will be needed is a multi-protocoll im like miranda.
but thats propably a major project and none i've got time for so far.

as for twitter, there's already an twitter client for android.
http://fredbrunel.com/journal/2007/11/introducing-twitterdroid/

> Muthu Ramadosshttp://www.intellibitz.comhttp://groups.google.com/group/android-chennaihttp://www.slideshare.net/intellibitz

[Muthu Ramadoss]

Twitter uses HTTP as correctly noted. Assuming Twitter supports XMPP how
would Android connect to it? Android GTalk is stepping away from XMPP to
its own mobile specific protocol.

An OpenIntents wrapper for HTTP + XML, REST based API's would be
fantastic. And let me see if I can continue this thought and do
something about it.

--
Thanks.

Muthu Ramadoss
http://www.intellibitz.com
http://groups.google.com/group/android-chennai

[Muthu Ramadoss]

Yes the worrying fact is the proposed incompatibility of GTalk with
XMPP. May be Google is trying to introduce a new open standard for
mobile communication.

Twitter is exposing only the HTTP api and not the XMPP one as per their
documentation.

--
Thanks.

Muthu Ramadoss
http://www.intellibitz.com
http://groups.google.com/group/android-chennai

[Zero]

take a look at the DeliciousApiHelper class in lib package. maybe you
can reuse some of this code.
a generic rest wrapper would be cool, although i'm not sure if its
possible with all the different api's out there.

> >> Muthu Ramadosshttp://www.intellibitz.comhttp://groups.google.com/group/android-chen...

[Muthu Ramadoss]

Sure, I'll look into DeliciousApiHelper. Thanks. I agree, OpenIntents
can support REST for atleast the popular services like Twitter, Facebook
etc.,

--
Thanks.

Muthu Ramadoss
http://www.intellibitz.com
http://groups.google.com/group/android-chennai