This is the jabber.org service notice for Wednesday, January 27, 2010.
There’s not as much to report today. The Isode team continues to track down the memory issues as well as a few less significant bugs and feature requests (DIGEST-MD5 login issues, vCard fixes, enabling chatroom logs, etc.). On the jabber.org team we are working to diagnose connection problems experienced by some users of Finch, Gajim, GNU Freetalk, Kopete, Meebo, Palringo, and a few other clients (most of the issues seem to be related to our disabling of the old SSL-only port 5223, but there might be other bugs involved). We also discovered an IP address that was making about 50 TCP connections a second without ever trying to start an XMPP stream, so we have blocked that IP address. We’re on the lookout for other abusive traffic, which might be causing more general problems at the jabber.org service.
Today we also held an impromptu meeting of jabber.org users in the jabber@conference.jabber.org chatroom. If our users would like us to hold a weekly meeting for a while, drop by the jabber@ chatroom and let us know (you can even join via the web as described on the help page).
Tomorrow (Thursday) we plan to fix a problem with our certificate chain, deploy several fixes from the Isode team, and track down more of the client connection problems mentioned above. We’ll keep you posted via identi.ca (mirrored to Twitter).
Peter Saint-Andre