This is the jabber.org service notice for Tuesday, January 26, 2010.
The team feels that it turned the corner yesterday and that we are on the path to a very stable and full-featured IM service. Some of the changes we’ve made are “behind the scenes” (better work processes for monitoring the service in real time, rotating logs to prevent a full disk on our server machine, etc.) so you won’t immediately notice them, but they are definitely improving reliability. In addition, the Isode team is hunting down some elusive bugs (e.g., regarding DIGEST-MD5 authentication, which is notoriously confusing for developers and has a lot of interoperability problems).
Our primary open issues are:
1. Memory usage. For reasons that we and Isode still don’t fully understand, memory usage slowly increases after a restart, causing the server run out of memory on the machine. We now have automated processes in place to restart the server when memory usage approaches the limit. This means that we’re having a few restarts every day, but they are controlled (even if not announced ahead of time). Fixing this problem is the top priority right now.
2. Google Talk connectivity. Some messages get lost from Google Talk to jabber.org. We’re working to figure out the conditions that cause this problem, because it is intermittent and might depend on which client you use.
3. vCards. Currently birthday and home page are not saved in user vCards. Isode is working to fix this relatively minor bug.
4. Chatroom logging. Currently this is disabled but we are working to bring it back so that we can archive the conversations from selected rooms at logs.jabber.org.
We will post again tomorrow with a full update, or follow our identi.ca feed (now also a Twitter feed) for regular status messages throughout the day.