Vacuum IM 1.2.0.1829 Beta / 1.0.2

Vacuum IM is an easy to use Jabber client that is just a plugin loader - all functionality is made available via plugins. This enforces modularity and ensures well defined component interaction via interfaces.

The minimum list of plug-ins necessary for work:
· accountmanager
· chatmessagehandler
· connectionmanager
· defaultconnection
· mainnwindow
· messageprocessor
· messagestyles
· messagewidgets
· normalmessagehandler
· notifications
· presence
· roster
· rosterchanger
· rostersmodel
· rostersview
· saslauth
· settings
· simplemessagestyle
· stanzaprocessor
· starttls
· statuschanger
· statusicons
· traymanager
· xmppstreams

Here are some key features of "Vacuum IM":

· Several independent profiles
· Multiple accounts in one profile
· Nested roster groups
· Support JID escaping
· Storage of history both locally and on the server, with the possibility of replication of history from the server to your computer
· Agreed off save messages (mode OTR)
· Full support for Jabber conferences
· Create a bookmark at the conference with the possibility autologin
· Support for CAPTCHA form, with the possibility of transmission without the use of browser
· A few named windows with tabs for chats and conferences
· Support for Adium message styles
· Animated Emoticons (using Adium style)
· Notifications of activity of the user in the chat
· Automatic change of transport with preservation of names, groups, subscriptions and archive messages
· Lists of privacy, with the possibility of ignoring or setting in invisible mode for individual contacts and groups
· Multi-stage automatic change of status depending on the time of inactivity
· Ability to set different status icons for individual contacts, and groups of contacts are connected through transport
· Support for avatars with the ability to specify a contact an arbitrary image as an avatar
· Ability to add annotation to contact

What's New in This Release: [ read full changelog ]

· Did not correctly handle changes in the participant's nickname when new nickname is already used by the same participant but from a different resource
· Incorrectly requested history of communication when connected to a server Openfire with plugin Open Archive
· The first message in the chat may not be saved in the local message archive
· Establishing a connection when transferring files could take up too much time
· File transfer could hang up from the cancellation of the transfer by the initiator
· Exchanging of chat state information with contact was disabled after receiving offline stored message from it
· The time of the delayed messages was not defined if it was send by XEP-0203: Delayed Delivery