<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://www.prosody.im/lib/exe/css.php?s=feed" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Prosody.im</title>
    <subtitle></subtitle>
    <link rel="alternate" type="text/html" href="http://www.prosody.im/"/>
    <id>http://www.prosody.im/</id>
    <updated>2012-02-05T04:18:23+00:00</updated>
    <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
<link rel="self" type="application/atom+xml" href="http://www.prosody.im/feed.php" />
    <entry>
        <title>Information for packagers - [Init script] </title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/packagers?rev=1327357905&amp;do=diff"/>
        <published>2012-01-23T22:31:45+00:00</published>
        <updated>2012-01-23T22:31:45+00:00</updated>
        <id>http://www.prosody.im/doc/packagers?rev=1327357905&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>Prosody's main goal is to be user-friendly and easy to use. One of the hardest parts of this task is getting the server installed and running in the first place. By providing reliable high quality packages then on most systems installing Prosody should take no more than a minute of the user's time.</summary>
    </entry>
    <entry>
        <title>Logging - Added section about log rotation</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/logging?rev=1326835008&amp;do=diff"/>
        <published>2012-01-17T21:16:48+00:00</published>
        <updated>2012-01-17T21:16:48+00:00</updated>
        <id>http://www.prosody.im/doc/logging?rev=1326835008&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>Prosody's logging configuration is very flexible. For those who want something simple however, this is also easy.

All log messages in Prosody have a 'level', which is basically a priority/urgency indicator. Most messages Prosody generates are at the 'debug' level, and can be safely ignored, unless you are trying to diagnose and/or report an issue. The next level is 'info', which is given to normal everyday messages about things happening on the server - client/server connections, for example. T…</summary>
    </entry>
    <entry>
        <title>prosodyctl</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/prosodyctl?rev=1326834644&amp;do=diff"/>
        <published>2012-01-17T21:10:44+00:00</published>
        <updated>2012-01-17T21:10:44+00:00</updated>
        <id>http://www.prosody.im/doc/prosodyctl?rev=1326834644&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>Prosody comes with a small utility to control the server, and manage users, etc. This is prosodyctl. It (currently) doesn't support Windows.

As an aid to those migrating from ejabberd, who may have existing scripts, prosodyctl is compatible with ejabberdctl wherever possible, this includes the register and unregister commands, despite these being hidden from the prosodyctl command listing by default.</summary>
    </entry>
    <entry>
        <title>Chatrooms</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/chatrooms?rev=1326337500&amp;do=diff"/>
        <published>2012-01-12T03:05:00+00:00</published>
        <updated>2012-01-12T03:05:00+00:00</updated>
        <id>http://www.prosody.im/doc/chatrooms?rev=1326337500&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>Setting up chatrooms in Prosody is a straightforward task. In Jabber/XMPP an entire subdomain is usually dedicated to hosting chatrooms. For example, if your main server is example.com, chatrooms would be served at conference.example.com.

Simply add a line to your config:</summary>
    </entry>
    <entry>
        <title>mod_muc</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/modules/mod_muc?rev=1326337073&amp;do=diff"/>
        <published>2012-01-12T02:57:53+00:00</published>
        <updated>2012-01-12T02:57:53+00:00</updated>
        <id>http://www.prosody.im/doc/modules/mod_muc?rev=1326337073&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>Multi-user chat (MUC) is Prosody's module for allowing you to create hosted chatrooms/conferences for XMPP users.

General information on setting up and using MUC chatrooms can be found in our 'Chatrooms' documentation, which you should read if you are new to XMPP chatrooms.</summary>
    </entry>
    <entry>
        <title>Developing Prosody modules - Add link to list of events.</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/developers/modules?rev=1325663346&amp;do=diff"/>
        <published>2012-01-04T07:49:06+00:00</published>
        <updated>2012-01-04T07:49:06+00:00</updated>
        <id>http://www.prosody.im/doc/developers/modules?rev=1325663346&amp;do=diff</id>
        <author>
            <name>Kim Alvefur</name>
        </author>
        <summary>Creating modules for Prosody is a piece of cake.

If you are new to Lua then take a look at the online Programming in Lua book for an introduction to the language, and the Lua manual for later reference. If you are already familiar with programming then Lua will hardly need learning at all.</summary>
    </entry>
    <entry>
        <title>Stanza - Describe stanza:get_text() and :get_child_text()</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/developers/util/stanza?rev=1324920958&amp;do=diff"/>
        <published>2011-12-26T17:35:58+00:00</published>
        <updated>2011-12-26T17:35:58+00:00</updated>
        <id>http://www.prosody.im/doc/developers/util/stanza?rev=1324920958&amp;do=diff</id>
        <author>
            <name>Kim Alvefur</name>
        </author>
        <summary>The stanza module provides several methods for building and manipulating stanza objects.

Utility functions

All of these functions create and return a new stanza object, on which you can call various methods, and which you may convert to a string of XML at any time with tostring(mystanza).</summary>
    </entry>
    <entry>
        <title>Testimonials</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/testimonials?rev=1323552649&amp;do=diff"/>
        <published>2011-12-10T21:30:49+00:00</published>
        <updated>2011-12-10T21:30:49+00:00</updated>
        <id>http://www.prosody.im/testimonials?rev=1323552649&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>People are talking about Prosody, we love it! Here are some of the nice words they have to say...

----------

“Just finished “upgrading” ejabberd to Prosody. Much smoother than I thought. Config is far, far simpler. I really, really &lt;3 Prosody :-)” @ivucica</summary>
    </entry>
    <entry>
        <title>0.6.2 Release Notes</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/release/0.6.2?rev=1323404359&amp;do=diff"/>
        <published>2011-12-09T04:19:19+00:00</published>
        <updated>2011-12-09T04:19:19+00:00</updated>
        <id>http://www.prosody.im/doc/release/0.6.2?rev=1323404359&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>This release is a bugfix release for the 0.6 stable branch.

Severe

	*  Disable SSLv2 by default
	*  Fix cases in XML handling which could emit invalid XML to clients
	*  Multiple signals in quick succession could send the server into a loop

Important

	*  Fix case where data sent immediately before a socket close could be lost
	*  Make [c2s|s2s]_require_encryption enforce encryption in all cases
	*  More robust detection of already-running Prosody instances
	*  Fix small memory leak in HTTP a…</summary>
    </entry>
    <entry>
        <title>LuaRocks - created</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/luarocks?rev=1323403289&amp;do=diff"/>
        <published>2011-12-09T04:01:29+00:00</published>
        <updated>2011-12-09T04:01:29+00:00</updated>
        <id>http://www.prosody.im/doc/luarocks?rev=1323403289&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>LuaRocks is a lightweight specialised package manager dedicated for installing Lua modules.

Usage

To install a module, simply run:
 luarocks install &lt;module name&gt;
You can also use the LuaRocks 'search' command to look for modules, and more. See luarocks --help for a full list.</summary>
    </entry>
    <entry>
        <title>Obtaining the source</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/source/start?rev=1323330951&amp;do=diff"/>
        <published>2011-12-08T07:55:51+00:00</published>
        <updated>2011-12-08T07:55:51+00:00</updated>
        <id>http://www.prosody.im/source/start?rev=1323330951&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>Obtaining the source

Prosody is open-source, under the MIT license. This means that the source code is freely available to download and use however you wish. You may modify the source code, and link it with closed-source applications. That said, we politely request that you do consider sending code improvements to us at the developer mailing list.</summary>
    </entry>
    <entry>
        <title>Download Prosody - Added a main cat &quot;Download Prosody&quot; sothat the site title is not &quot;Debian and Ubuntu&quot;</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/download/start?rev=1323217190&amp;do=diff"/>
        <published>2011-12-07T00:19:50+00:00</published>
        <updated>2011-12-07T00:19:50+00:00</updated>
        <id>http://www.prosody.im/download/start?rev=1323217190&amp;do=diff</id>
        <author>
            <name>Simon</name>
        </author>
        <summary>Prosody is available for all of the major operating systems. Be sure to check out the release notes.



Select a package for your system from the list, or download the source:

Debian and Ubuntu

A binary package is available that should work on Debian Lenny, and Ubuntu 8.04 (Hardy) up to 10.04 (Lucid).</summary>
    </entry>
    <entry>
        <title>Installing Prosody - &quot;Gentoo&quot;</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/install?rev=1323216969&amp;do=diff"/>
        <published>2011-12-07T00:16:09+00:00</published>
        <updated>2011-12-07T00:16:09+00:00</updated>
        <id>http://www.prosody.im/doc/install?rev=1323216969&amp;do=diff</id>
        <author>
            <name>Simon</name>
        </author>
        <summary>Installing Prosody is quite straightforward in most cases. We have packages for the major operating systems to make it even easier. If we have no package for yours, you should be able to install using the source package, see  below.

Debian/Ubuntu

After downloading the package file, simply double-click on it to perform the installation.</summary>
    </entry>
    <entry>
        <title>mod_groups</title>
        <link rel="alternate" type="text/html" href="http://www.prosody.im/doc/modules/mod_groups?rev=1322584534&amp;do=diff"/>
        <published>2011-11-29T16:35:34+00:00</published>
        <updated>2011-11-29T16:35:34+00:00</updated>
        <id>http://www.prosody.im/doc/modules/mod_groups?rev=1322584534&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>mod_groups was designed to allow administrators to create virtual groups of users that automatically see each other in their contact lists. The shared groups will be sent to the user along with their usual roster without overriding or permanently adding the contacts. There is no need for the user to authorise the these contacts in their contact list - this is done automatically on the server.</summary>
    </entry>
</feed>

