Differences between version 2 and previous revision of JabberNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Sunday, April 18, 2004 7:13:17 pm | by AristotlePagaltzis | Revert |
| Older page: | version 1 | Last edited on Sunday, April 18, 2004 6:45:31 pm | by AristotlePagaltzis | Revert |
@@ -1,47 +1,17 @@
!!! Client notes
!! WLUG Jabber server
-Because you're a WLUG'ger you might want to use the jabber.meta.net.nz server, kindly hosted by Cuchulain and Isomer.
(If demand increases we might put a Jabber server up on the WlugServer).
-
-!! Using foreign transports
-
-Chances are you have an ICQ or MSN account and a lot of people you'd like to keep in touch with, while you get them all converted to also using Jabber. Servers can run transports, which are server-side conversions between Jabber's XML and the native tongue of other [IM] systems.
-
-For example, you can add the JIT Transport (Jabber ICQ transport) at jit.jabber.meta.net.nz. Fill in your ICQ account details, and it will automatically pull down your server-stored ICQ contact list and add them to your Jabber roster. They get given JIDs of ''uin''@jit.jabber.meta.net.nz, and can be addressed as such.
-
-Add as many transports as you want, and have a play around.
-
-!! Multiple logins 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 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).
-
-!! Offline messages
-
-If you are not online when a message is sent to you, your [Jabber] server will hold it for you until you next connect
.
+Because you're a WLUG'ger you might want to use the jabber.meta.net.nz server, kindly hosted by [
Cuchulain]
and [
Isomer]
. (If demand increases we might put a Jabber server up on the WlugServer).
!! Tkabber: conference actions
Click on the __Subject:__ to get a list of actions.
-
-!! Using Transports
-
-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]
-
-__Note__: the [DNS] names below are fictional, make sure you check what your [Jabber] server uses.
-
-[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.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].
----
!!! Server notes
!! [Debian]: newly registered users get a 401 error on log in attempt
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.
