So I spent way to much time trying to figure out exactly how Adium and Meebo handle updating nicknames in a buddy list (roster). The answer is, while they are both based on libpurple/gaim they both pretty much ignore setting the nickname in presence updates and messages. Let’s just say I spent a lot of time figuring out exactly how adium deals with this: i.e. doing traces through libpurple’s source code: http://www.google.com/codesearch?hl=en&q=+libpurple..,
I tried to find a socks proxy where I could rewrite packets and watch jabber messages, but I couldn’t find anything that quite fit my needs, so I ended up modifying something called PySocks (which hasn’t been updated in a few years, and required a bit of hacking to evne run, but works quite well as a socks proxy for rewriting packets and monitoring jabber to figure out what’s going on. [sourceforge.net/projects/pysocks/]
So google codesearch, grep, and pysocks was the method, but what was the result? And why does this matter to you?
Good questions self!
The idea is to have your hab.la buddy list become more personal, so instead of having visitors appear as “webuser1” and “webuser2”, they’ll appear as “John the Spammer”, and “Fred the friendly reader”. I.e. your buddy list will not only tell you you have 2 people browsing your site, but also who those people are [if they’ve chatted with you using hab.la in the past]
Hab.la building relationships – sounds like a good motto to me :-)
Comments [0]