-
Top Commenters
-
Community
-
Popular Threads
-
Recent Comments
- I'm w/ Rex. Always enjoyed your imagery. Reminds me of Beagle Bros. software catalog sensibilities, or, even better, Baba Ram Dass' "Be Here Now" book. Tickling the mind's eye ....
- I find you images filled with wit, Dave. The more obscure the reference, the more I enjoy them.
- lol @ Kenneth. I think I'm going to coin that phrase and start using it. Who knows maybe it'll start a trend. That is way to f'ing funny. So that brings me up to November of last year.... Comcast ...
- Until the client side of the equation is smarter, decentralizing an inherently centralized, server-oriented application like Twitter without Twitter's explicit cooperation is always going to be next to ...
- hmmm. while I agree. I never questioned AWS costing money. and it seems the more valuable part of getting me to pay $0.18 a month - was to get me to pay anything. once that exchange happens - then the ...
XMPP as the basis for interop in TwitterLand? (Scripting News)
12 comments
-
Joe Beda 3 months ago with 2 points
I'm sure the Google Talk team would love to have you build an app on top of Talk. (I switched off the Talk team a little while ago). However, based on what I think you want out of twitter, talking to Google that way may not be what you want.
There are two ways to talk XMPP/Jabber. The first is C2S -- where you write a client that can connect to a server. You can write a bot to connect to the Google server, but be aware that you may hit some limits as we really built the system for users, not bots.
The other way is S2S -- where you are another server that connects to Talk. The name of your bot/service wouldn't be @gmail.com but would rather be hosted on your own server with your own domain. In this case you have a lot more freedom to implement the server in whatever way you want. This is the way the twitter bot interacts.
There is *really* a lot to like about XMPP S2S. It is very open much in the model of SMTP. When a message to "joebob@mydomain.com" is seen, the server will do a DNS lookup (SRV record), call that server and deliver the message. Check out xmpp.org for all of the specifications and a list of server implementations to start playing with. If you want to be *really* fancy you can write your own server, but I would suggest you start with something off the shelf to play with. -
We are also doing XMPP notifications at Seesmic. PubSub is being worked on now.
-
i'm trying the same thing.
-
Did you see that TLS and SASL PLAIN are required for authentication with gtalk?
You could try working with OpenFire to get started it's reasonably easy to use as a server.
http://www.igniterealtime.org/projects/openfire... -
Does XMPP support a pub-sub style interface, or would it have to be layered over it? Broadcast by having the originator unicast to every follower seems inefficient.
-
> Does XMPP support a pub-sub style interface
yes, you can read all about it here: http://www.xmpp.org/extensions/xep-0060.html
If you're interested in writing something with Openfire, you can check out the XMPP bot that I wrote for Openfire to do instant notifications of RSS changes, it's a component that lives inside the server, much like what Joe talked about above:
http://cephas.net/projects/instantfeeds/
Cheers,
AJ -
Additionally, see also Ralph Meijer's presentation Federated Social Networks.
He's the co-author of XEP-0060, was at Jaiku and is the developer of Idavoll, an implementation of a generic publish-subscribe service component for Jabber servers, which now supports an HTTP-XMPP Pubsub gateway. ;)
See also, this Jaiku thread. -
I seem to recall a Scoble interview with the twitter guys where they mentioned that twitter used jabber under the hood
-
Very nice.....I have been asking for this for a while now. With Twitter crashing during Mac Expo.....and everyone talking about using micro blogging for disaster support scenarios a decentralized micro blogging would be huge!
-
This has been in the air for a while - http://serendipity.ruwenzori.net/index.php/2007...
I guess it is slowly creeping into everyone's mindshare... -
Take a look at ISS (Instant Syndicating Standards). ISS is a set of open standards that enable people to discover and syndicate information within their social network. It blends the Web and XMPP in an elegant way.
-
Twitter *is* based on XMPP.


