Free xmpp software for linux

sendxmpp project is a perl-script to send xmpp (jabber), similar to what mail does for mail.
sendxmpp was written by me, Dirk-Jan C. Binnema, and is available under the term of the GNU General Public License v2. The hard work is done by Ryan Eatmons Net::XMPP-modules, and you need have them installed for sendxmpp to work.
Obviously, you also need a jabber account; they are freely available at jabber.org, but you can also run your own server.
sendxmpp is in use on computers around the globe, for example for distributing CVS-commit alerts, sending server warnings and notifying users.
Example:
Suppose you have to manage a remote server somewhere, and you have to keep an eye on its cpu load-average. You could write a script to check this, and run it periodically from cron. This script could contain something like:
if test "$cpuload" -gt "$CPULOADMAX"; then
top -b -n 1 | sendxmpp -s "wake up! cpu load $cpuload at `hostname`" someone@jabber.org
fi
And on my client machine, my jabber-client wil pop-up a message, depending on your client. There are many different client, for any platform/OS.
Installation:
unpack the tarball, and enter the new directory
$ perl Makefile.PL
$ make
$ make install
Enhancements:
- This version brings some documentation improvements and also you specify non-default port numbers for jabber servers.

xmppjca project is a JCA 1.5 resource Adapter for managing connections to a XMPP (aka jabber) server from a J2EE application server (for instance JBoss). The resource adapter has been written to conform to the JCA 1.5 specification but only JBoss has been tested. The RA uses the smack API to connect to XMPP servers.

The connector supports multiple connections to multiple servers and provides an abstraction of the underlying smack api that in addition to connection management provides support for extensions from su-smack which includes support for JEP-0060 aka publish subscribe.

Currently the RA only supports container managed security. Future versions will support bean managed security using JAAS. The goal is eventually support single-sign-on using SASL+GSSAPI to XMPP servers which support this mechanism.

Currently the RA does not support transactions. The precise way in which this will be supported is a matter of debate.

Installation

The project consists of two parts - xmppjca and xmppjca-spec. Build both artifacts. Deploy the rar-file in your J2EE-server. In a standard JBoss- installation this means copying the rar-file to $JBOSS_HOME/server/default/deploy. The xmppjca-spec-< version >.jar should be placed in the classpath of clients who need to use the resource adapter. In a standard JBoss-installation the easiest way is to copy the file to $JBOSS_HOME/server/default/lib. In most situations the application server will hotdeploy the rar-file but not the jar- file so a restart is needed whenever you update the spec-file.

Empathy 2.26.2 / 2.27.3 gives an application which functions as a Gnome IM/voice/video client reusing Gossips UI and using Nokias Mission Control. It has a rich set of reusable instant messaging widgets, and a GNOME client using those widgets. It uses Telepathy and Nokias Mission Control, and reuses Gossips UI.

gloox is a high-level Jabber/XMPP library for C++. Additionally, it offers high-level interfaces for interaction with an XMPP server. gloox is released under the GNU GPL. Commercial licenses are available.

gloox is fully compliant to XMPP Core and almost fully compliant to XMPP IM.

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, its 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.

SNIMMER stands for Single Network Instant Messaging Mediation and Relay. SNIMMER can talk to any IM network, and can relay instant messages from one IM network to another.

Currently, one cannot use AOL messenger to chat with users on MSN, Yahoo!, or GTalk and vice-versa. SNIMMER overcomes instant messenger non-interoperability.

It has been designed primarily to help webmasters to chat with Web visitors on any IM network using any instant messenger.

What you will need:

1) Internet connection
2) IM account that you always use
3) Create a set of IM accounts for all networks (eg. AOL, ICQ, Yahoo, MSN) that you want to receive visitors from. It is essential that you create brand new accounts that were not used by you for personal chat, otherwise snimmer will clash with you online.
4) Web server where you can run a CGI script. A sample script that comes with this package is written in python but you can re-write it in your favorite language - it is very simple.
5) You neeed Python to be installed on your web server. Also you will need python-xmpp library installed too.

You can grab python here: http://www.python.org/

XMPPPY library download:

http://sourceforge.net/project/showfiles.php?group_id=97081&package_id=103821

6) You should know how to add CGI scripts to pages and how to display results. Sample script works but youll probably want a better integration with your page.
7) You have to know what jabber servers and what jabber transports you are going to use.

You can deploy your own or you can try the ones that are publicly available. You can refer to this page to find the server for you:

http://www.jabber.org/user/publicservers.shtml

In the simplest case youll need to replace example.com with the name of the server you have picked. Though it is not neccessary that transport should be on the same server. You can use transports from other servers if their policies allow that.

How to install it:

1) get it from http://www.snimmer.com/snimmer/snimmer.tar and unpack it
2) open credentials.py with a text editor. You will see something like this (lines numbers are added for readability - they should not be present in the actual file):

1 clients={
2 snimmer@example.com:{
3 login:snimmer,
4 server:example.com,
5 password:snimmer,
6 transports:{
7 xmpp:(example.com,,),
8 # icq:(icq.example.com,123456789,ICQ_password,),
9 # yahoo:(yahoo.example.com,Yahoo_login,Yahoo_password),
10 # msn:(msn.example.com,MSN_login@hotmail.com,MSN_password),
11 # aim:(aim.example.com,AIM_screenname,AIM_password),
13 },
14 },
15
16 ## This is another connection. If you want to be able to receive two calls at the same time
17 ## uncomment it. To receive even more calls - add more such sections
18 # snimmer2@example.com:{
19 # login:snimmer2,
20 # server:example.com,
21 # password:snimmer,
22 # transports:{
23 # icq:(icq.example.com,123456780,ICQ_password2,),
24 # },
25 # },
26
27 }
28
29 SPOOL=rc:snimmerspool
30 SPOOL=r/tmp/snimmerspool
31
32 publisher_im=icq
33 publisher_screenname=123456789
34
35 blocked_ips=blocked.txt

The G System, often simply called "G", is an effort to create exactly this: simulation of evolution. This is both, a scientific exercise and a virtual reality where many "users" can participate in an ever changing, realistic and ... evolving universe.
G is basically a framework for virtual world simulations. And not only a framework (the "G System") but a virtual reality itself, which will become the application created with the G System.
- Multi-User 3D virtual world experience. The G System provides a 3D virtual reality that can be experienced by many users at the same time. The Users are part of the evolving universe.
- Simulation. The goal of G is to simulate a realistic, dynamic and evolving universe. To allow great flexibility a well designed core system provides the infrastructure for the world. The whole world is made up with elements.
Elements allow for creation of rule systems (like realistic physics, impact of feelings,...) to be applied to elements as well as integration of artificial intelligence (and anything else that is needed) to create evolutionary abilities.
Rule systems are created with "agents". These agents can reach arbitrary complexity and are executed as a thread, thus allowing maximum freedom to the agent design. Users can enter the world and interact with their environment, which ultimately has an impact on the evolution of the virtual universe. Thus, users make up a part of the overall simulation.
Enhancements:
LIBRARIES
G Core System (GCS):
- GCS::GObject does not store the IDs of the children anymore
- GCS::GWorldData can now return a list of children of an element
G World Engine (GWE):
- Bugs fixed concerning connecting to the G Universe
- Mutex deadlocks fixed that prevented the demo to run
- XMPP Presence subscriptions are now handled and in use
- Added new GStorage class wich implements a Qt based database layer, every database supported by Qt is supported by the G System, tested and known to work so far: QSQLITE, QMYSQL3, QPSQL7
- GStorage now used instead of GXmlStorage
- All GXmlNetwork related classes have been removed
- Fixed iterator bug that could cause crashes
- The factory has been adapted to the new database options
BINARIES
guniverseclient:
- Extracted the communication/chat area into a separate widget
- Now differentiates between internal and external contacts in the
- contact list.
- The default configuration file is now in $HOME/.guniverseclient.xml
- This makes it easy to have different configurations for every user
MISC
installer:
- 2 questions less

libstrophe is a library for XMPP client and component communication. Our goal is to build a library that is portable, usable quickly, reliable, well documented and that implements the XMPP specification.
Main features:
- XMPP compliant
- Platform agnostic
- TLS support (coming soon)
- SASL DIGEST-MD5 and SASL PLAIN authentication
- Legacy jabber authentication
- Resource binding
- Low-level miniDOM access for manipulating stanzas
- Event handers for timed events, stanza names and/or namespaces, stanza ids
- Threadsafe (coming soon)
- High-level stanza object manipulation and handling (coming soon)
- Full documentation (coming soon)
- Customizable logging and allocation facilities
- C++ binding (coming soon)
Enhancements:
- fix a bug in the fallback to jabber auth that prevented login to jabberd 1.4 servers
- Simplify access to the default loggers, and merge the basic_logging and basic examples
- draft C++ api