Changeset 0fd8559 for doc


Ignore:
Timestamp:
2007-02-18T17:48:04Z (18 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
0f4c1bb5
Parents:
8de63c3 (diff), c7d0f41 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Merging new Jabber module. See the massive changelog for all the cool
improvements. :-)

Location:
doc
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • doc/CHANGES

    r8de63c3 r0fd8559  
    4141    and password for the existing connection.
    4242  * Per-account settings (see the new "account set" command).
     43- A brand new Jabber module. Besides the major code cleanup, it also has
     44  has these new features:
     45  * Pretty complete XMPP support: RFC3920, RFC3921 plus a number of XEPs
     46    including XEP73 and XEP85. (See http://www.xmpp.org/ for what all these
     47    things mean exactly.) Privacy lists are not supported for obvious
     48    reasons.
     49  * This complete support also includes TLS and SASL support and SRV record
     50    lookup. This means that specifying a server tag for connections should
     51    (almost) never be necessary anymore, BitlBee can find the server and can
     52    automatically convert plaintext connections to TLS-encrypted ones.
     53  * XEP85 means typing notifications. The older XEP22 (still used by some
     54    clients including Gaim <2.0) is not supported.
     55  * Better handling of buddies who have more than one resource on-line. As
     56    long as one resource is on-line (and visible), BitlBee will show this.
     57    (The previous module didn't keep track of resources and sent an offline
     58    event as soon as any resource disappears.)
     59  * You can now set your resource priority.
     60  * The info command now gives away state/message information for all
     61    resources available for that buddy. (Of course this only works if the
     62    buddy is in your contact list.)
    4363
    4464Version 1.0.3:

  • doc/user-guide/commands.xml

    r8de63c3 r0fd8559  
    3030                                <description>
    3131                                        <para>
    32                                                 Note that the servertag argument is optional. You only have to use it if the part after the @ in your handle isn't the hostname of your Jabber server, or if you want to use SSL/connect to a non-standard port number. The format is simple: [&lt;servername&gt;[:&lt;portnumber&gt;][:ssl]].
     32                                                The handle should be a full handle, including the domain name. You can specify a servername if necessary. Normally BitlBee doesn't need this though, since it's able to find out the server by doing DNS SRV lookups.
     33                                        </para>
     34
     35                                        <para>
     36                                                In previous versions it was also possible to specify port numbers and/or SSL in the server tag. This is deprecated and should now be done using the <emphasis>account set</emphasis> command. This also applies to specifying a resource in the handle (like <emphasis>wilmer@bitlbee.org/work</emphasis>).
    3337                                        </para>
    3438                                </description>
    35 
    36                                 <description>
    37                                         <para>
    38                                                 Google Talk uses the Jabber protocol. Please note that Google talk is SSL-only, but officially reachable over both port 5222 and 5223. Usually BitlBee users have to connect via port 5223, for example like this:
    39                                         </para>
    40                                 </description>
    41 
    42                                 <ircexample>
    43                                         <ircline nick="wilmer">account add jabber example@gmail.com hobbelmeeuw talk.google.com:5223:ssl</ircline>
    44                                         <ircline nick="root">Account successfully added</ircline>
    45                                 </ircexample>
    4639                        </bitlbee-command>
    4740
    … …  
    517510        </bitlbee-setting>
    518511
     512        <bitlbee-setting name="priority" type="integer" scope="account">
     513                <default>0</default>
     514
     515                <description>
     516                        <para>
     517                                Can be set for Jabber connections. When connecting to one account from multiple places, this priority value will help the server to determine where to deliver incoming messages (that aren't addressed to a specific resource already).
     518                        </para>
     519
     520                        <para>
     521                                According to RFC 3921 servers will always deliver messages to the server with the highest priority value. Mmessages will not be delivered to resources with a negative priority setting (and should be saved as an off-line message if all available resources have a negative priority value).
     522                        </para>
     523                </description>
     524        </bitlbee-setting>
     525
    519526        <bitlbee-setting name="private" type="boolean" scope="global">
    520527                <default>true</default>
    … …  
    556563        </bitlbee-setting>
    557564
     565        <bitlbee-setting name="resource_select" type="string" scope="account">
     566                <default>priority</default>
     567                <possible-values>priority, time</possible-values>
     568
     569                <description>
     570                        <para>
     571                                Because the IRC interface makes it pretty hard to specify the resource to talk to (when a buddy is online through different resources), this setting was added.
     572                        </para>
     573
     574                        <para>
     575                                Normally it's set to <emphasis>priority</emphasis> which means messages will always be delivered to the buddy's resource with the highest priority. If the setting is set to <emphasis>time</emphasis>, messages will be delivered to the resource that was last used to send you a message (or the resource that most recently connected).
     576                        </para>
     577                </description>
     578        </bitlbee-setting>
     579
    558580        <bitlbee-setting name="save_on_quit" type="boolean" scope="global">
    559581                <default>true</default>
    … …  
    593615                        <para>
    594616                                If BitlBee fails to detect this sometimes (most likely in AIM messages over an ICQ connection), you can set this setting to <emphasis>always</emphasis>, but this might sometimes accidentally strip non-HTML things too.
     617                        </para>
     618                </description>
     619        </bitlbee-setting>
     620
     621        <bitlbee-setting name="tls" type="boolean" scope="account">
     622                <default>try</default>
     623
     624                <description>
     625                        <para>
     626                                Newer Jabber servers allow clients to convert a plain-text session to a TLS/SSL-encrypted session. Normally (with this setting set to <emphasis>try</emphasis>) BitlBee will do this, if possible.
     627                        </para>
     628
     629                        <para>
     630                                If you want to force BitlBee to use TLS sessions only (and to give up if that doesn't seem to be possible) you can set this setting to <emphasis>true</emphasis>. Set it to <emphasis>false</emphasis> if you want the session to remain plain-text.
    595631                        </para>
    596632                </description>
Note: See TracChangeset for help on using the changeset viewer.