Powered By:
Clearspace
BlatherSource: Because development won't keep quiet
11

You've probably at least seen:

http://florianjensen.com/2008/01/17/aol-adopting-xmpp-aka-jabber/

 

So I played with this a little yesterday .. very cool!  I certainly hope that AOL does indeed go through with this and embrace XMPP!  Based off my experience with OSCAR and XMPP, they -could- accomplish everything they're currently doing with OSCAR with XMPP.  Do they want to?  Is this simply a gateway to their AIM and ICQ services?  Who knows, but it's good to see!  I would imagine AOL has already seen how excited folk are about this, probably by their poor test server getting suddenly wailed on.  I can only hope they won't decide this is a bad idea.  The thing is, people like to use AIM and ICQ.  People like to use XMPP.  Why do they have to be at odds?  AOL's take on how chatting should work could bring wonderful improvements to XMPP overall.  I think Google's joining the fray did a lot of good for XMPP in general in terms of XEPs that came about because of it and such.  And people like me wouldn't be spending so much time building transports or multi-protocol clients if we didn't at some level like the services we were connecting to.  For example, I don't hate AIM.  I simply like a lot of protocols and don't want to run 8 different chat clients on my desktop.  I also think the OSCAR protocol is interesting, as are the other protocols, so I wanted to learn more about them.  Does that mean I'm out to make XMPP overtake AIM?  Hell no.  To be frank, it would be a happy day to me if the transports were no longer necessary, if people on AOL's servers could chat with people on my own server and on jabber.org's server and on lots of others without having to figure out the protocols.  Does this mean no one would try to dissect the protocols anymore?  Probably not.  Part of the drive of that is learning and understanding.  It doesn't have to be about trying to circumvent.

 

Imagine if AOL decided they really liked XMPP overall and ditched OSCAR though.  That would hose old clients.  But what if they released a new client that spoke XMPP while keeping their old servers going?  Furthermore, what if that client could point at other servers than AOLs.  Now AOL has a nice client or two out there for any XMPP clients to use.  That's kinda cool!  There's plenty of great XMPP servers out there at this point.  The client choices in general are a little lacking.  Spark, of which I'm in charge of nowadays, is pretty, it's cross platform, but it's a beast.  Java is not necessarily great in terms of small memory footprint.  Coccinella has a lot of cool features but it's Tcl/Tk and I've never liked the "feel" of Tcl/Tk.  Google Talk, there's not a version for my OS, so what good does it do me.  iChat...  nothing personal Apple but I've never liked it.  I can't put my finger on why really.  It's also hard to explain why I don't use Psi for everyday use.  I love it for development.  Nothing is better IMO.  But for some reason it didn't feel simple enough to be something I want to use as a regular client.  Adium X and Pidgin?  It's the primary client I use but it lacks a lot of XMPP functionality (though it's definitely improving on that front)  All of these are good clients, and have good followings, but there's still a lot of room for other 'entries' to come into the mix.  Nothing seems to "do it" for everyone yet.  Of course, who knows if that will ever happen.  But seriously AOL, I'd love to see you throw your hat into the mix!

 

Now what about MSN and Yahoo and others?  Yahoo, I could see them possibly embracing XMPP.  Hell they bought Zimbra and Zimbra's suite has XMPP capabilities nowadays, so they have some bought expertise there.  MSN on the other hand, they sell a product (LCS? OCS?  whatever it is) that may be a good drive -not- to embrace XMPP.  I don't know much about OCS or LCS though.

 

Overall though, this kind of reminds me of e-mail.  Everyone can have their own implementations of email services and such, that doesn't mean we can't all speak the same language!  AOL, I hope you take all this attention as a compliment!  I think we're all proud and pleased to see you express an interest in XMPP and maybe join the family!!!

11 Comments 0 References Permalink
2

I've been quiet for a bit.  Most of you know how blogging goes ... you get excited about it or have a lot to talk about for a time, and then you start doing less and less posting.  Though some of you are quite adept at regularly posting ... to you I give the virtual thumbs up.  =)  But what have I been up recently?  Quite a bit actually.

 

For those who don't know, I left my university job of 11 years at the end of October and joined Jive Software.  My work with Jive fell right in line with "what I really want to do" for my career.  =)  Plus, they're all really great people.  That said, I'm working from across the country (waves) and quite enjoying it.  Maybe Jive will open up a Raleigh-Durham (Research Triangle Park?) office at some point.  ;D ;D ;D  Anyway.  I have continued my IM Gateway work, become one of the primary developers of Openfire, and become the lead developer of Spark (amongst other things).  I've been enjoying all of these things quite a bit!  I don't get to spend a lot of time on Spark, but when I do, it's quite fun to be playing with the client side again.  It's been a loooong time.  At this point I get to play with all three of the main areas of XMPP (Client, Server, and Component)!  It didn't take that long to adapt to Jive's environment though.  I actually really dig more deadlines and scheduled releases and such.  Frankly, it helps me mind "pick a target" when I'm trying to decide what to work on next.

 

So what's happened to PyICQt and PyAIMt?  I've officially stepped aside.  I moved them to Google Code so that others can more easily become involved.  You can now find them at:

http://code.google.com/p/pyaimt/

and

http://code.google.com/p/pyicqt/

I haven't removed myself as one of the "owners" yet on there so that it's possible for me to facilitate others becoming involved in the project for the next month or so in case others have been dying to get involved and didn't think about approaching me before.  A couple of other folk have stepped up and are doing a few things with it!  Yay!   The new location of the py-transports "mailing list" is now a Google Group at http://groups.google.com/group/py-transports.  I must admit, at this point, I don't miss them.  I do hope that they keep going though as I do believe they are good projects.

 

What about the XMPP Script Repository?  Well, I moved that to SourceForge: http://xmppscriptrepo.sf.net/

I won't be actively managing it, but if you are interested in becoming involved with it, please ping me and I'll set you up!  (let me know what your sourceforge id is)  It's using a SourceForge tracker to handle new script submissions.  If people -do- submit things to it, that would be about the most maintenance it needs unless you really feel like doing some significant work with it.  So... lemme know!

 

So what's left of BlatherSource?  You're "looking at it".  All I'm using BlatherSource for at this point is my blog.  I may do something else with it at some point, but for now it's just my blog.  I did like the interface I had put together for it, but I just don't have time to keep developing it/to manage it, ya know?  Many kudos to my hosts at Modevia.com for putting up with my requests for the site.  =)

 

I do still have a site for JWGC, http://jwgc.sf.net/ (moved it to SourceForge).  No idea if I'll ever do much else with it, but I like to keep it around.  It's my first XMPP related project ever.  =)

 

So... why did I move PyAIMt and PyICQt to Google Code instead of SourceForge?  Well, mostly because I wanted a wiki for the documentation and I couldn't find one on SourceForge.  Of course, an hour after moving everything I found that SourceForge -does- have a wiki.  Color me blind...  Doesn't matter, was neat to see what Google Code offers in terms of services.  I really like their "easy on the end user" issues tracker.  I don't like their web space offering though.  Spaces I think it is?  Whatever it is I don't like it.  I couldn't do with it anything like what I wanted.  I hear they are looking into a better solution at some point, so that might be cool.

 

After looking around relentlessly or a Java OTR library .. something like libotr that Pidgin uses, I decided to request a project on SourceForge to write my own.  Hopefully others will find use in it.  It's not approved yet, but if it is, it'll be jotr.  (http://sourceforge.net/projects/jotr ?)  If anyone is interesting in helping me out with that, I would greatly appreciate it!  I was rather surprised to see nothing already exists for Java for OTR.  (then again, I could have just not found it, but I tried really hard to find it  ;D  )

 

The IM Gateway plugin ended up putting me in the lead developer role of Java-JML (http://java-jml.sf.net) (MSN messenger library for Java) and also a developer of Martyr (http://martyr.sf.net/) (IRC library for Java).  Things sure do pile up quick, don't they?  =)  Those have been fun though.  I've gotten to work with Smack a little more as well in my Jive work, so that's been cool.  At this point I feel like I'm touching just about everything!  lol  Who knew that I'd go from being irritated with Java to enjoying working with it so much.

 

Anyway, so that's what my life has been lately!  New job, new adventures, letting go of some of the old ... moving forward.  =)  Yes, I do still have some XEPs to write/propose on the backburner.  I just haven't gotten to the point where I need to write them.

2 Comments 0 References Permalink