Differences between version 39 and predecessor to the previous major change of JabberInstantMessaging.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 39 | Last edited on Wednesday, March 24, 2004 5:25:54 am | by AristotlePagaltzis | Revert |
| Older page: | version 37 | Last edited on Friday, March 19, 2004 11:51:40 am | by PerryLorier | Revert |
@@ -1,75 +1,70 @@
-!! Introduction
+!
!! Introduction
Like most things proprietary, OpenSource people have written their own InstantMessenger, called [Jabber]. [Jabber] is built on a robust model, similar to [SMTP] and [HTTP] - and completely unlike [IRC]'s unscalable mess :) It is based on a core [XML] router with small plugin modules handling all the various parts of the [InstantMessaging|InstantMessenger]. It supports "Transports" which allow a Jabber user to talk to users of other InstantMessenger networks such as [AIM], [MSN], [ICQ], YahooMessenger, [SMTP], [IRC], [IMAP] and many others. It has clients for MicrosoftWindows, [Linux], various [PDA]'s and other machines/devices.
You may want a nice simple introduction to SettingUpJabber. PerryLorier has also written a JabberWiki.
-!!Clients for Linux
-![GTK]/[GNOME]
-* [Gabber] for [GNOME] (uses [GTK])
-* [Gaim], a multiprotocol [GTK2] [InstantMessenger] which has a [Jabber] plugin
-* [Gnome Jabber | http://gnome
-jabber.sourceforge.net/], a newcomer which is full of [GTK2] goodness. (The web page says that the author has stopped development of this and is working with the Gossip authors.)
-* [Gabber2 | http://gabber.jabberstudio.org/], the [GTK2] port of [Gabber]. Still in development.
-* [Gossip | http://gossip.imendio.org/], another [GTK2] Jabber client
-* Tkabber, it's ui sucks, but it's very feature complete.
+----
-![Qt]/[KDE]
-* [Psi|http://psi.affinix.com/]
for [Qt]
-* [Konverse|http://konverse.sourceforge.net] for [KDE]. Webpage was last updated in 2001.
-* [Kopete|http://kopete.kde.org/] for [KDE]. Seems to be the main IM client for [KDE].
+!!! Clients
for Linux
-!
Console
-* [imcom|http://imcom.floobin.cx/] for console (requires [Python])
-* [jabmsg|https
://sourceforge
.net/projects/jabmsg/] batch-mode Jabber message sender (requires [Perl])
-* [CenterIcq], a multiprotocol [Curses] [InstantMessenger] which has a [Jabber] plugin
+; %%% [GTK]/[GNOME] :
+** [Gabber] for [GNOME] (uses [GTK])
+** [Gaim], a multiprotocol [GTK2] [InstantMessenger] which has a [Jabber] plugin
+** [Gnome Jabber | http://gnome-jabber.sf.net/], a newcomer which is full of [GTK2] goodness. (The web page says that the author has stopped development of this and is working with the Gossip authors.)
+** [Gabber2 | http://gabber.jabberstudio.org/], the [GTK2] port of [Gabber]. Still in development.
+** [Gossip | http://gossip.imendio.org/], another [GTK2] Jabber client
+; %%% [Qt]/[KDE] :
+** [Psi | http://psi.affinix.com/], the canonical [Qt] client
+** [Kopete | http://kopete.kde.org/], [KDE]'s main multiprotocol IM client.
+** [Konverse | http://konverse.sf.net] for [KDE]. Webpage was last updated in 2001.
+; %%%
Console :
+*
* [imcom | http://imcom.floobin.cx/] for console (requires [Python])
+*
* [jabmsg | http
://sf
.net/projects/jabmsg/] batch-mode Jabber message sender (requires [Perl])
+*
* [CenterIcq], a multiprotocol [Curses] [InstantMessenger] which has a [Jabber] plugin
+; %%% MicrosoftWindows :
+** [Exodus | http://exodus.jabberstudio.org/] for MicrosoftWindows
+** Jabber.com's client for MicrosoftWindows. (Current version seems to only let you connect to Jabber.com's server)
+** [JAJC | http://jajc.ksn.ru/] for MicrosoftWindows
+** [Rhymbox | http://www.rhymbox.com/], [MSN] Messenger for Jabber. Looks *really* nice in Windows XP
+; %%% Others :
+** [Tkabber | http://tkabber.jabber.ru/], written in [TCL]/[Tk] (requires a couple of extra [TCL] libraries) so this should run on any OperatingSystem that [TCL]/Tk runs on. It's UserInterface sucks, but it's very feature complete.
+** [Nitro | http://nitro.jabberstudio.org/] for [MacOSX]
-!!Clients for MicrosoftWindows
-* [Exodus|http://exodus.jabberstudio.org/] for MicrosoftWindows
-* Jabber.com's client for MicrosoftWindows. (Current version seems to only let you connect to Jabber.com's server)
-* [JAJC|http://jajc.ksn.ru/] for MicrosoftWindows
-* [Rhymbox|http://www.rhymbox.com/], [MSN] Messenger for Jabber. Looks *really* nice in Windows XP
+----
-!!Other Platforms
-* [tkabber|http://tkabber.jabberstudio.org/index_en.html], written in [TCL]/[Tk] (requires a couple of extra [TCL] libraries) so this should run on any OperatingSystem that [TCL]/Tk runs on.
-* [Nitro|http://nitro.jabberstudio.org/] for [MacOSX]
+!!! Client notes
-----
-Client notes
+!! Multiple logins on the same account
-* You can log in multiple times on the same account - this
is what the "resource" is. So you could log in from different machines, and give each a different resource name. %%% %%%
-*
If a message is sent to just your id
(without specifying a resource) then it goes to whichever of your clients has the highest "priority" (which you can set at log in time). %%% %%%
-* If you are not online when a message is sent to you, your jabber server will hold it for you until you next connect
.
+This
is what the "resource" is. So you could log in from different machines, and give each a different resource name. If a message is sent to just your account
(without specifying a resource) then it goes to whichever of your clients has the highest "priority" (which you can set at log in time).
-----
-Client-specific notes
+!! Offline messages
-! tkabber
-*
If you are part of
a conference
, you can click on the __Subject:__ to get a list of actions
.
+If you are not online when
a message is sent to you
, your [Jabber] server will hold it for
you until you next connect
.
-----
-Running a Jabber Server
-Having trouble getting the Jabber server under Debian working? Here are some hints.
+!! Tkabber: conference actions
-!I register as a new user and it won't let me login, I get a 401 error message.
-Debian commented out
the __mod
_auth
_plain__ module from their sample config, presumably
to pressure users into using secure authentication methods. While this is
a worthy goal, they overlooked that creating new users uses __mod_auth_plain__. If you uncomment this module it will work
.
+Click on
the __Subject:
__ to get
a list of actions
.
-----
-
+!! Using Transports
-Your jabber server will have
a list of transports you can use. These will provide communications with
other services,
such as multiuser conferencing, ICQ, AIM, Yahoo, MSN, IRC, or even SMTP (ie, standard email
). Normally they
have descriptive names like '
icq.jabber.org'
so are easy to guess, but it pays to have a lot at the transports available
.
+Transports provide
a gateway to
other communication
services such as multiuser conferencing, [
ICQ]
, [
AIM]
, Yahoo, [
MSN]
, [
IRC]
, or even [
SMTP]
(ie [Email]
). Your [Jabber] server will
have a list of transports you can use, normally with
descriptive names like __
icq.jabber.org__
so they
are easy to guess.
+!! Transport options for [ICQ]
-!ICQ transport
+__Note__: the [DNS] names below are fictional, make sure you check what your [Jabber] server uses.
-There are two main implementations of this around the place.
ICQ and AIM actually use the same protocol, so the AIM-t transport can be used as an
ICQ transport
as well. There is also a
JIT transport which
handles ICQ and ICQ-SMS a lot better than the AIM-t transport.
+[
ICQ]
and [
AIM]
actually use the same protocol, so the AIM-t transport can be used for [
ICQ]
as well. However, the
JIT transport handles [
ICQ] messaging
and ICQ-SMS a lot better than the AIM-t transport.
-If your jabber
server uses the AIM-t transport, you should subscribe to the icq.jabber.domain
.whatever
agent, using your ICQ username and password, and then you can add contacts of the form icqid@icq.jabber.domain
.whatever
. You can send SMS's
by sending something like
-
SEND-SMS:+cellphonenumber:<message>
-to any ICQ recipient on
your jabber list
.
+If your [Jabber]
server uses the AIM-t transport, you should subscribe to the icq.jabber.example
.net
agent, using your ICQ username and password, and then you can add contacts of the form icqid@icq.jabber.example
.net
. You can send [
SMS] messages
by sending something like the following to any [ICQ] recipient on your roster: __
SEND-SMS:+cellphonenumber:<message>__
+
+If
your [Jabber] server uses the JIT transport, then use that instead. Its a lot nicer, supports user searching correctly, handles [SMS] better, so on. You can add contacts of the form icqid@jit.
jabber.example.net for [ICQ], or phonenumber@sms.jabber.example.net for [SMS].
+
+----
+!!! Running a Jabber Server
-If your jabber server uses the JIT transport, then use it instead of AIM-t. Its a lot nicer, supports user searching correctly, handles
[SMS
] better, so
on.
-Subscribe as above (check what the agent is actually called first!).
-You can add contacts of the form icqid@jit.jabber.domain.whatever, for icq, or phonenumber@sms.jabber.domain.whatever for sms.
+!!
[Debian
]: newly registered users get a 401 error
on log in attempt
-NOTE: all server names mentioned above are guides only, make sure you get
the correct DNS name of the transport for your jabber server!
+The __mod_auth_plain__ module is commented out in
the package sample configuration, presumably to prod users to use secure authentication methods. Unfortunately, creating new users requires __mod_auth_plain__. Uncomment this module and registration will work.
