<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://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://prosody.im/"/>
    <id>http://prosody.im/</id>
    <updated>2012-05-17T17:07:44+01:00</updated>
    <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
<link rel="self" type="application/atom+xml" href="http://prosody.im/feed.php" />
    <entry>
        <title>mod_compression - [Configuration] 7 is now default.</title>
        <link rel="alternate" type="text/html" href="http://prosody.im/doc/modules/mod_compression?rev=1337120227&amp;do=diff"/>
        <published>2012-05-15T23:17:07+01:00</published>
        <updated>2012-05-15T23:17:07+01:00</updated>
        <id>http://prosody.im/doc/modules/mod_compression?rev=1337120227&amp;do=diff</id>
        <author>
            <name>Kim Alvefur</name>
        </author>
        <summary>While the bandwidth usage of XMPP isn't great, compressing the data sent to/from your server can give significant benefits to those on slow connections, such as dial-up or mobile networks. Prosody supports compression for client-to-server (if your client supports it) and server-to-server streams using the mod_compression plugin.</summary>
    </entry>
    <entry>
        <title>Installing modules - created</title>
        <link rel="alternate" type="text/html" href="http://prosody.im/doc/installing_modules?rev=1336756674&amp;do=diff"/>
        <published>2012-05-11T18:17:54+01:00</published>
        <updated>2012-05-11T18:17:54+01:00</updated>
        <id>http://prosody.im/doc/installing_modules?rev=1336756674&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>Most of Prosody's functionality is implemented through plugins/modules (the two terms are used interchangeably). Sometimes you will want to install additional modules that are not supplied with Prosody.

Paths

By default Prosody looks in a single directory for a module, and this is set at build time. On a standard Linux system such as Debian, you might expect to find it somewhere like /usr/lib/prosody/modules/.</summary>
    </entry>
    <entry>
        <title>XMPP</title>
        <link rel="alternate" type="text/html" href="http://prosody.im/doc/xmpp?rev=1336755049&amp;do=diff"/>
        <published>2012-05-11T17:50:49+01:00</published>
        <updated>2012-05-11T17:50:49+01:00</updated>
        <id>http://prosody.im/doc/xmpp?rev=1336755049&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>Prosody is an XMPP server. But what exactly is XMPP?

	&quot; The Extensible Messaging and Presence Protocol (XMPP) is an open technology for real-time communication, which powers a wide range of applications including instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.
 - - xmpp.org&quot;</summary>
    </entry>
    <entry>
        <title>Server-to-server XMPP - created</title>
        <link rel="alternate" type="text/html" href="http://prosody.im/doc/s2s?rev=1336695104&amp;do=diff"/>
        <published>2012-05-11T01:11:44+01:00</published>
        <updated>2012-05-11T01:11:44+01:00</updated>
        <id>http://prosody.im/doc/s2s?rev=1336695104&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>XMPP allows for servers communicating seamlessly with each other, forming a global 'federated' IM network. This architecture is very similar email, where someone on gmail.com can send an email to someone with an account on hotmail.com, for example.

Prosody supports server-to-server (s2s) connections out of the box. All you need for it to work is:</summary>
    </entry>
    <entry>
        <title>Setting up a BOSH server - [Tested clients] Updated link for Candy</title>
        <link rel="alternate" type="text/html" href="http://prosody.im/doc/setting_up_bosh?rev=1336644571&amp;do=diff"/>
        <published>2012-05-10T11:09:31+01:00</published>
        <updated>2012-05-10T11:09:31+01:00</updated>
        <id>http://prosody.im/doc/setting_up_bosh?rev=1336644571&amp;do=diff</id>
        <author>
            <name>Kim Alvefur</name>
        </author>
        <summary>BOSH (previously known as HTTP binding or “http-bind”) is a technology to use XMPP over HTTP, the protocol that powers the web. This allows XMPP applications to run in web pages, but also any other HTTP-only environment such as behind restrictive firewalls.</summary>
    </entry>
    <entry>
        <title>Prosody Modules</title>
        <link rel="alternate" type="text/html" href="http://prosody.im/doc/modules?rev=1336085420&amp;do=diff"/>
        <published>2012-05-03T23:50:20+01:00</published>
        <updated>2012-05-03T23:50:20+01:00</updated>
        <id>http://prosody.im/doc/modules?rev=1336085420&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>This is a list of Prosody modules, both core (distributed with Prosody) and third-party.
Name       Description                                 Specs  Notes            First version  announce    Broadcast message to online users           Supported by Psi, Gajim and other clients  0.5  admin_adhoc  Service Administration  XEP-0133   0.8  admin_telnet     Telnet admin console                        Previously mod_console  0.2  bosh        BOSH (XMPP over HTTP) support for Prosody  XEP-0124 XEP-02…</summary>
    </entry>
    <entry>
        <title>Authentication providers - [Providers] Add auth modules from prosody-modules which have a wiki page.</title>
        <link rel="alternate" type="text/html" href="http://prosody.im/doc/authentication?rev=1336084755&amp;do=diff"/>
        <published>2012-05-03T23:39:15+01:00</published>
        <updated>2012-05-03T23:39:15+01:00</updated>
        <id>http://prosody.im/doc/authentication?rev=1336084755&amp;do=diff</id>
        <author>
            <name>Kim Alvefur</name>
        </author>
        <summary>Starting with version 0.8, Prosody supports authentication provider plugins. These can either use Prosody's built-in storage drivers (e.g. to use a custom format for account data), or they can integrate with external storage and authentication APIs.

Selecting a provider

A provider can be selected with the “authentication” option. This can be set globally and/or per-host.</summary>
    </entry>
    <entry>
        <title>Configuring Prosody - [Virtual host settings] Add a bit about authentication. It might deserve a bit more text</title>
        <link rel="alternate" type="text/html" href="http://prosody.im/doc/configure?rev=1336084459&amp;do=diff"/>
        <published>2012-05-03T23:34:19+01:00</published>
        <updated>2012-05-03T23:34:19+01:00</updated>
        <id>http://prosody.im/doc/configure?rev=1336084459&amp;do=diff</id>
        <author>
            <name>Kim Alvefur</name>
        </author>
        <summary>Prosody's configuration is held in a single file, prosody.cfg.lua. If you install Prosody under GNU/Linux then you should find it in /etc/prosody/prosody.cfg.lua. On Mac OS X installed via Homebrew you should find it in /usr/local/etc/prosody/prosody.cfg.lua. On other systems, or when not installed, it will be under the same directory as the prosody main executable.</summary>
    </entry>
    <entry>
        <title>Prosody HTTP server</title>
        <link rel="alternate" type="text/html" href="http://prosody.im/doc/http?rev=1336072656&amp;do=diff"/>
        <published>2012-05-03T20:17:36+01:00</published>
        <updated>2012-05-03T20:17:36+01:00</updated>
        <id>http://prosody.im/doc/http?rev=1336072656&amp;do=diff</id>
        <author>
            <name>Matthew Wild</name>
        </author>
        <summary>Prosody contains a mini built-in HTTP server, which is used for BOSH and other modules.

The following HTTP modules are supplied with Prosody:

	*  mod_bosh
	*   mod_http_files

To enable HTTP, simply load mod_http by adding it to your config:


    modules_enabled = {
        ...
        &quot;http&quot;;
        ...
    }</summary>
    </entry>
</feed>

