palaver 0.3 review

palaver is a multi-user chat component for Jabber and XMPP servers

License: MIT/X Consortium License File size: 37K Developer: palaver Team

0

palaver is a multi-user chat component for Jabber and XMPP servers. The intention for this project is to support all features of JEP-0045 as well as the relevant extended discovery features of JEP-0128.

palaver is written in Python using the Twisted framework for Internet applications. It is licensed under the open source MIT license.

The main inspiration for writing palaver was to replace JCR mu-conference. While mu-conference has served the community well, it's lack of maintenance has left many searching for a replacement.

Currently all basic multi-user chat features are supported, including some extra things like ban lists. More features are on the way, and the intention is to fully support the entire protocol.

palaver is licensed under the MIT open source license. It is free to use, modify and distribute by commercial and non-commercial users and developers.

Requirements:
Twisted Core 2.1.0 or greater
Twisted Words 0.3 or greater
a Jabber or XMPP server which supports components

Note: that palaver and the server do not need to run on the same machine or share any code.

Installation

Palaver utilizes Python's distutils build and install system. You can install Palaver with:

python setup.py install

Please see the distutils documentation for more information on options. A commonly used option is --prefix=PATH to specify where the install should occur (this defaults to the standard site-packages directory for Python).

What's New in This Release:
This release adds a PostgreSQL backend, a convert script from the legacy XML spool to the PostgreSQL backend, 'player' role and affiliation, destroying of rooms, support for legacy room creation and JEP room creation with instant rooms, the ability for other message elements to be broadcast and put in history, and invitation support.
It fixes a bug when a presence of type error was sent, a bug where legacy messages only went to legacy clients, and other minor bugfixes.