Changeset 8e9e2b7 for doc


Ignore:
Timestamp:
2010-10-03T02:45:26Z (14 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
04f0c10
Parents:
88de0c9 (diff), 2af3e23 (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 mainline, which includes a huge msnp13 merge.

Not 100% sure about the OpenSSL merge, should double check that but I'm
currently offline.

Location:
doc
Files:
5 edited

Legend:

Unmodified
Added
Removed

  • doc/CHANGES

    r88de0c9 r8e9e2b7  
    44http://bugs.bitlbee.org/bitlbee/timeline?daysback=90&changeset=on
    55
    6 Version 1.3dev:
    7 - For the first time since 2007, a dev snapshot. Like then, this is pretty
    8   stable already (running on testing.bitlbee.org for weeks by now), but not
    9   all planned features for the next major release are ready yet, and there
    10   may be some rough edges in the interface and documentation.
    11 - Loads of new stuff, mostly ready for a new major release, but starting with
    12   a dev snapshot. A few changes that were planned for a long time already:
     6Version
     7- Important: This version drops backward compatibility with the file format
     8  used for user settings in versions before 1.2. If you're upgrading from
     9  very old BitlBee versions (like 1.0.x), you'll have to recreate your
     10  BitlBee account - or use an 1.2.x BitlBee once to do the conversion.
    1311- Rewrote the IRC core, which brings:
    1412  * Support for multiple (control) channels, so you can have one channel per
    … …  
    5250    for a list of supported protocols (works only in libpurple-enabled
    5351    binaries).
     52- Rewritten MSN module, implementing MSNP15 instead of the old MSNP8:
     53  * MSNP8 support from MSN was getting pretty unreliable. There were issues
     54    with remembering display names and adding contacts/auth requests (or
     55    even contacts silently getting blocked!). This upgrade should fix all
     56    of that.
     57  * Support for sending offline messages.
     58  * Support for setting and reading status messages.
    5459- Support for file transfers, in and out. /DCC SEND a file to a contact and
    5560  it becomes a file transfer, and incoming file transfers become /DCC SENDs
    … …  
    5863- Updated Yahoo! module to be in sync again with libyahoo2. This mostly
    5964  fixes issues with authorization requests.
    60 
    61 Finished 6 Aug 2010
     65- Show if a contact is mobile or not. See "help set mobile_is_away".
     66- Easier handling of XMPP chatroom invitations.
     67- The chatroom mode of the Twitter module is now enabled by default, since
     68  this was by far the most popular. To disable it, see "help set mode".
     69- Added some Twitter-specific commands that can only be used in the Twitter
     70  window. Most important addition: Retweets. See "help set commands".
     71- Removed some ancient account/nick migration scripts and added one for
     72  easier switching from Pidgin and other libpurple-based clients to BitlBee.
     73- Many bug fixes in both the core and IM modules, small feature enhancements
     74  and other minor changes.
     75
     76Finished ...
    6277
    6378Version 1.2.8:

  • doc/FAQ

    r88de0c9 r8e9e2b7  
    6262   These days, we replaced the Yahoo! code with libyahoo2 (which is a
    6363   separate Yahoo! module. It's derived from Gaim, but separately
    64    maintained) and wrote our own MSN module. More modules are probably going
    65    to be changed, so in the near future, the API might be the only thing
    66    left from Gaim.
    67 
    68 Q: What's that Gaim doing in BitlBee error messages and my Jabber resource?
    69 A: Ah, well, as you probably know we use some of Gaim's IM-modules, and we
    70    don't think it's worth our time to do a search-and-replace over the whole
    71    source to get rid of every reference to Gaim. In fact, we don't want to,
    72    since we don't want to pretend we wrote all that code.
     64   maintained) and wrote our own MSN, Jabber and Twitter modules from
     65   scratch. Most of the API has also been changed, so by now the only traces
     66   of Gaim left are in the "nogaim" filename.
    7367   
    74    About Jabber: If you want a different resource string, you can set it
    75    when logging in by appending it to your Jabber ID, like:
    76    lintux@jabber.com/BitlBee
     68   There is good news for Gaim (or now Pidgin, of course) fans though:
     69   BitlBee can now be compiled to use libpurple for all IM interactions.
     70   This makes BitlBee a bit more resource-hungry, but adds support for many
     71   IM protocols/networks that couldn't be used from BitlBee so far.

  • doc/README

    r88de0c9 r8e9e2b7  
    7171--otr=1 or --otr=0 to force it on or off, respectively.
    7272
    73 These days, MSN Messenger clients have to connect to the MS Passport servers
    74 through HTTPS. BitlBee can use several SSL libraries for this: GnuTLS, NSS
    75 (which comes with Mozilla) and OpenSSL. OpenSSL is not GPL-compatible in some
    76 situations, so using GnuTLS or NSS is preferred. However, especially on *BSD,
    77 OpenSSL can be considered part of the operating system, which eliminates the
    78 GPL incompatibility.
     73These days, many IM protocols use SSL/TLS connections (for authentication
     74or for the whole session). BitlBee can use several SSL libraries for this:
     75GnuTLS, NSS (which comes with Mozilla) and OpenSSL. OpenSSL is not GPL-
     76compatible in some situations, so using GnuTLS is preferred. However,
     77especially on *BSD, OpenSSL can be considered part of the operating system,
     78which eliminates the GPL incompatibility.
    7979
    8080The incompatibility is also the reason why the SSL library detection code

  • doc/user-guide/commands.xml

    r88de0c9 r8e9e2b7  
    16551655                                Only the <emphasis>group list</emphasis> command is supported at the moment, which shows a list of all groups defined so far.
    16561656                        </para>
     1657                       
     1658                        <para>
     1659                                If you want to move contacts between groups, you can use the IRC <emphasis>/invite</emphasis> command. Also, if you use the <emphasis>add</emphasis> command in a control channel configured to show just one group, the new contact will automatically be added to that group.
     1660                        </para>
    16571661                </description>
    16581662        </bitlbee-command>

  • doc/user-guide/misc.xml

    r88de0c9 r8e9e2b7  
    175175
    176176<para>
    177 If you want to configure your own channels, you can use the <emphasis>channel set</emphasis>.
     177If you want to configure your own channels, you can use the <emphasis>channel set</emphasis> command. See <emphasis>help channels3</emphasis> for more information.
     178</para>
     179
     180</sect1>
     181
     182<sect1 id="channels3">
     183<title>Configuring a control channel</title>
     184
     185<para>
     186The most important setting for a control channel is <emphasis>fill_by</emphasis>. It
     187tells BitlBee what information should be used to decide if someone should be shown
     188in the channel or not. After setting this setting to, for example, <emphasis>account</emphasis>, you
     189also have to set the <emphasis>account</emphasis> setting. Example:
     190</para>
     191
     192<ircexample>
     193        <ircline nick="wilmer">chan set &amp;wlm fill_by account</ircline>
     194        <ircline nick="root">fill_by = `account'</ircline>
     195        <ircline nick="wilmer">chan set &amp;wlm account msn</ircline>
     196        <ircline nick="root">account = `msn'</ircline>
     197</ircexample>
     198
     199<para>
     200Also, each channel has a <emphasis>show_users</emphasis> setting which lets you
     201choose, for example, if you want to see only online contacts in a channel, or
     202also/just offline contacts. Example:
     203</para>
     204
     205<ircexample>
     206        <ircline nick="wilmer">chan set &amp;offline show_users offline</ircline>
     207        <ircline nick="root">show_users = `offline'</ircline>
     208</ircexample>
     209
     210<para>
     211See the help information for all these settings for more information.
    178212</para>
    179213
    … …  
    234268</sect1>
    235269
     270<sect1 id="whatsnew010206">
     271<title>New stuff in BitlBee 1.2.6</title>
     272
     273<para>
     274Twitter support. See <emphasis>help account add twitter</emphasis>.
     275</para>
     276</sect1>
     277
     278<sect1 id="whatsnew010300">
     279<title>New stuff in BitlBee 1.3dev</title>
     280
     281<para>
     282Support for multiple configurable control channels, each with a subset of
     283your contact list. See <emphasis>help channels</emphasis> for more
     284information.
     285</para>
     286
     287<para>
     288File transfer support for some protocols (more if you use libpurple). Just
     289/DCC SEND stuff. Incoming files also become DCC transfers.
     290</para>
     291
     292<para>
     293Only if you run your own BitlBee instance: You can build a BitlBee that uses
     294libpurple for connecting to IM networks instead of its own code, adding
     295support for some of the more obscure IM protocols and features.
     296</para>
     297
     298<para>
     299Many more things, briefly described in <emphasis>help news1.3</emphasis>.
     300</para>
     301</sect1>
     302
    236303<sect1 id="news1.3">
    237 <title>New stuff in BitlBee 1.3dev</title>
     304<title>New stuff in BitlBee 1.3dev (details)</title>
    238305
    239306<para>
Note: See TracChangeset for help on using the changeset viewer.