Pidgin 2.6.x: Houston, we have a problem

<p>Well, we have less-than-good news. We'll get straight to the point.<br /><br /><strike>The latest versions of Pidgin, 2.6.x, are not really suitable for monitoring LibraryH3lp queues. If you use a 2.6.x Pidgin to answer questions from queues in a multi-librarian environment, you are at risk for leaving patrons hanging when librarians change shift.<br /><br />This is a big deal. Since the beginning, Pidgin has been the main external LibraryH3lp client used on the PC. It is open source, supports plugins, and is multi-protocol, so librarians can be signed into lots of different accounts as needed. Most importantly for LibraryH3lp, it always sent the Jabber protocol standard "gone" <a href="http://xmpp.org/extensions/xep-0085.html">notification</a> back to the server when the librarian closed a conversation window. This is a critical piece of the routing system that allows LibraryH3lp to work effectively in a multi-operator environment.<br /><br />With 2.6.x, if a patron's original librarian has closed the patron's conversation window and signed all the way out of their account, new messages from that same patron will go off into the ether rather than getting routed to other librarians on the queue. Those messages will not appear until that original librarian signs back into their account, which may be hours, days, or even weeks later.<br /><br />So, what can you do if you've been using 2.6.x?<br /><br />The easiest thing is to stop immediately and downgrade. Version 2.5.9 is the most recent release that sends the "gone" notification. It was only distributed in source code format. We have compiled it for LibraryH3lp users and you can <a href="http://c0361712.cdn.cloudfiles.rackspacecloud.com/pidgin-2.5.9.exe">download it here</a>. Happily, you can just run the installer and it will keep all of your existing preferences and account information.<div><br />We have a ticket in with the Pidgin developers to see if they will resume sending "gone" on window close in the future. No word yet, but we'll update when we know more.</strike><br /><br />[edited 1/10/2010 Any version of Pidgin, or any other XMPP client, can be used now. There is no longer a dependency on "gone" in the routing system]<br /><br />In happier external client news, the <a href="http://www.digsby.com/">Digsby</a> developers were <a href="http://forum.digsby.com/viewtopic.php?id=4024">very responsive</a> to a request to start sending the "gone" command. Digsby is now a <a href="http://libraryh3lp.com/docs/suitable-jabber-clients.html">suitable client</a> for use with LibraryH3lp queues! Digsby also displays LibraryH3lp queue avatars and pulls the patron's IP address and referring URL extremely quickly; Pidgin takes about 30 seconds and doesn't display the queue avatars at all yet. Additionally, Digsby has a slick little floating chat window that sticks in the foreground while you keep a web page up. Very handy for chatting, researching, and sending links all at the same time as us librarians do so frequently. But this all warrants its own blog post... coming soon.<br /><br /></div></p>

Well, we have less-than-good news. We'll get straight to the point.The latest versions of Pidgin, 2.6.x, are not really suitable for monitoring LibraryH3lp queues. If you use a 2.6.x Pidgin to answer questions from queues in a multi-librarian envir…

SMS Gateway (Android variety) updated

<p>Back in March, we released the <a href="http://libraryh3lp.blogspot.com/2009/03/sms-gateway-released.html">first version</a> of our Android phone SMS gateway. It worked great on the original G1 phones, but then new models came out. A few libraries purchased G2 (Mytouch 3G or HTC Magic) phones and had problems, even though the phone's operating system should be the same.<br /><br />Thanks to Derik Badman from Temple University physically shipping us one of these phones, the problem is solved. We were able to connect his phone to Eric's Mac and debug it pretty easily, once we had our hands on the actual device.<br /><br />While we were working on the problem, we learned a couple of things that led us to add visible features to the phone portion of the application:<br /><ol><li>Now, when you press the Start and Stop buttons, the phone displays feedback that the app actually started or stopped. </li><li>There is a place to enter your phone's telephone number. As it turns out, not all Android phones actually know their own phone number, and without it, the LibraryH3lp gateway fails to deliver messages. Now, there is a field in the application where you can provide the phone's number. This is a lot easier than trying to get your mobile provider to correct this over the air.</li></ol>The app should also work with international phone numbers now. We know it works for at least two libraries in two different non-US countries, anyway.<br /><br />The updated app has the Android SMS gateway working for all libraries we're currently aware of that want to use it. Let us know if you're having trouble with it.<br /><br />Derik, your phone is in the mail.</p>

Back in March, we released the first version of our Android phone SMS gateway. It worked great on the original G1 phones, but then new models came out. A few libraries purchased G2 (Mytouch 3G or HTC Magic) phones and had problems, even though the…