[LWN Logo]
[LWN.net]
From:	 Rahul Dave <rahul@reno.cis.upenn.edu>
To:	 lwn@lwn.net
Subject: Jabber Weekly News, Issue 1
Date:	 Wed, 29 Aug 2001 16:36:23 -0400
Cc:	 rahul@reno.cis.upenn.edu


Jabber Weekly News for 29th August, 2001
========================================
Issue 1
=======

Hi,
This is the first of a weekly newsletter designed to let the world know the 
interesting stuff thats happening in the Jabber Community. This newsletter
will soon be available as a RSS channel, please stay tuned. We will also point to
RSS channels of individual projects and JIG's(Jabber interest groups).
Corrections, more information, etc can be sent to me at rahul@mozdev.org.
If there is interest I can add a section on news about clients, and another
one for the efforts of commercial companies. So please send me feedback!
Rahul

Latest Jabber News
-------------------

The Jabber Software Foundation has been formally incorporated. See
http://foundation.jabber.org for details.

JabberCon was a big success, with many nice presentations 
(http://www.jabbercon.com/schedule.html), and an on the fly
collaboration between the jabber team and independent developer Dave Winer on 
connecting blogs to jabber using the Blogger API. This led to the
Jabber-RPC spec.  There is a writeup on the 
spec in the Jabber RPC folder of the new
jabnews site: http://jabnews.manilasites.com/directory/20.


A writeup on the convention by Peter is at http://www.jabber.org/?oid=2001.

DJ Adams announced Jabber::RPC, an implementation of the Jabber-RPC 
formalisation, in Perl, that provides client and server stubs with 
which you can write Jabber-RPC requesters (in the form of Jabber clients) 
and Jabber-RPC responders (in the form of Jabber clients or Jabber
components) (http://www.pipetree.com/jabber/jrpc/).

He also announced Jabber::RPC::HTTPgate, a separately installable module
that provides a two-way gateway between the Jabber-based and HTTP-based
XML-RPC worlds. It allows Jabber-based requesters (i.e. Jabber-RPC
clients) to call HTTP-based responders (i.e. 'traditional' XML-RPC
web-server-based servers), and HTTP-based requesters (i.e. 
'traditional' XML-RPC clients) to call Jabber-based responders (i.e.
Jabber-RPC servers) (http://www.pipetree.com/jabber/jrpc/httpgate/).

On the blog front again, Jogger, a jabber powered blog was announced. 
You can find out more at http://jogger.jabber.org.

The Muse project has a communications API which interfaces to different communications
systems. It has modules for Napster, Gnutella, and Jabber. You can find out more at:
http://www.echomine.org/projects/muse/.

Jabber RSS
----------
The GNOME Jabber client, Gabber, has an RSS Feed at 
http://gabber.sourceforge.net/gabber.rss.

The Standards JIG has an RSS feed at 
http://www.pipetree.com/jabber/sc-jig/sc-jig.rss

By prepending http://www.pipetree.com/rss? to the above URL's you can get a 
html'ization of the feed:
http://www.pipetree.com/rss?http://gabber.sourceforge.net/gabber.rss
http://www.pipetree.com/rss?http://www.pipetree.com/jabber/sc-jig/sc-jig.rss.


Jabber Links
------------

The home of the Jabber project is at http://www.jabber.org.

The Jabber Software Foundation, which co-ordinates activities pertaining
to the community code-base is at http://foundation.jabber.org.

A large listing of jabber clients can be found at http://www.jabbercentral.com.