Changeset bb09b3c for doc


Ignore:
Timestamp:
2010-06-03T21:13:57Z (14 years ago)
Author:
Sven Moritz Hallberg <pesco@…>
Branches:
master
Children:
1dd3470
Parents:
a6b2f13 (diff), df1ae622 (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:

merge in bitlbee 1.2.7

Location:
doc
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • doc/CHANGES

    ra6b2f13 rbb09b3c  
    33
    44http://bugs.bitlbee.org/bitlbee/timeline?daysback=90&changeset=on
     5
     6Version 1.2.7:
     7- Fixed problems with MSN Messenger authentication. ("Could not parse
     8  Passport server response")
     9- Fixed broken typing notifications when talking to GTalk contacts.
     10- Fixed an issue with non-anonymous Jabber chatrooms polluting the nick
     11  namespace, sometimes generating odd warning messages.
     12- Restored ability to start groupchats on ICQ.
     13- Added show_offline setting that will also show offline contacts in the
     14  control channel.
     15- OAuth support for Twitter: This means the module will keep working after
     16  June (this also changes "via API" under your tweets into "via BitlBee").
     17
     18Finished 15 May 2010
     19
     20Version 1.2.6a:
     21- Fixed a typo that renders the Twitter groupchat mode unusable. A last-
     22  minute change that came a few minutes late.
     23
     24Finished 19 Apr 2010
    525
    626Version 1.2.6:

  • doc/user-guide/commands.xml

    ra6b2f13 rbb09b3c  
    7979                                                To send tweets yourself, send them to the twitter_(yourusername) contact, or just write in the groupchat channel if you enabled that option.
    8080                                        </para>
     81
     82                                        <para>
     83                                                Since Twitter now requires OAuth authentication, you should not enter your Twitter password into BitlBee. Just type a bogus password. The first time you log in, BitlBee will start OAuth authentication. (See <emphasis>help set oauth</emphasis>.)
     84                                        </para>
    8185                                </description>
    8286                        </bitlbee-command>
    … …  
    776780        <bitlbee-setting name="halfop_buddies" type="string" scope="global">
    777781                <default>encrypted</default>
    778                 <possible-values>encrypted, trusted, notaway, false</possible-values>
     782                <possible-values>encrypted, trusted, notaway, online, false</possible-values>
    779783
    780784                <description>
    … …  
    784788                       
    785789                        <para>
    786                                 If "false", the flag is never set. On "notaway", the flag is removed for users marked as "away" and set for all others. On "encrypted", the flag is set for users with whom we have an encrypted connection. On "trusted", it is set only for encrypted connections using a trusted key.
     790                                If "false", the flag is never set. On "notaway", the flag is removed for users marked as "away" and set for all others. On "encrypted", the flag is set for users with whom we have an encrypted connection. On "trusted", it is set only for encrypted connections using a trusted key. On "online", the flag is set whenever the user is online; only meaningful in conjunction with "show_offline".
    787791                        </para>
    788792                </description>
    … …  
    834838        <bitlbee-setting name="op_buddies" type="string" scope="global">
    835839                <default>trusted</default>
    836                 <possible-values>encrypted, trusted, notaway, false</possible-values>
     840                <possible-values>encrypted, trusted, notaway, online, false</possible-values>
    837841
    838842                <description>
    … …  
    842846                       
    843847                        <para>
    844                                 If "false", the flag is never set. On "notaway", the flag is removed for users marked as "away" and set for all others. On "encrypted", the flag is set for users with whom we have an encrypted connection. On "trusted", it is set only for encrypted connections using a trusted key.
     848                                If "false", the flag is never set. On "notaway", the flag is removed for users marked as "away" and set for all others. On "encrypted", the flag is set for users with whom we have an encrypted connection. On "trusted", it is set only for encrypted connections using a trusted key. On "online", the flag is set whenever the user is online; only meaningful in conjunction with "show_offline".
    845849                        </para>
    846850                </description>
    … …  
    882886        </bitlbee-setting>
    883887
     888        <bitlbee-setting name="message_length" type="integer" scope="account">
     889                <default>140</default>
     890
     891                <description>
     892                        <para>
     893                                Since Twitter rejects messages longer than 140 characters, BitlBee can count message length and emit a warning instead of waiting for Twitter to reject it.
     894                        </para>
     895
     896                        <para>
     897                                You can change this limit here but this won't disable length checks on Twitter's side. You can also set it to 0 to disable the check in case you believe BitlBee doesn't count the characters correctly.
     898                        </para>
     899                </description>
     900
     901        </bitlbee-setting>
     902
    884903        <bitlbee-setting name="mode" type="string" scope="account">
    885904                <possible-values>one, many, chat</possible-values>
    … …  
    925944        </bitlbee-setting>
    926945
     946        <bitlbee-setting name="oauth" type="boolean" scope="account">
     947                <default>true</default>
     948
     949                <description>
     950                        <para>
     951                                This enables OAuth authentication for Twitter accounts. From June 2010 this will be mandatory.
     952                        </para>
     953
     954                        <para>
     955                                With OAuth enabled, you shouldn't tell BitlBee your Twitter password. Just add your account with a bogus password and type <emphasis>account on</emphasis>. BitlBee will then give you a URL to authenticate with Twitter. If this succeeds, Twitter will return a PIN code which you can give back to BitlBee to finish the process.
     956                        </para>
     957
     958                        <para>
     959                                The resulting access token will be saved permanently, so you have to do this only once.
     960                        </para>
     961                </description>
     962
     963        </bitlbee-setting>
     964
    927965        <bitlbee-setting name="ops" type="string" scope="global">
    928966                <default>both</default>
    … …  
    10601098        </bitlbee-setting>
    10611099
     1100        <bitlbee-setting name="show_offline" type="boolean" scope="global">
     1101                <default>false</default>
     1102
     1103                <description>
     1104                        <para>
     1105                                If enabled causes BitlBee to also show offline users in Channel. You may want to adjust the settings "voice_buddies", "halfop_buddies" and "op_buddies" according to your liking. A reasonable candidate is "voice_buddies=online", "halfop_buddies=false", "op_buddies=notaway".
     1106                        </para>
     1107                        <para>
     1108                                This option takes effect as soon as you reconnect.
     1109                        </para>
     1110                </description>
     1111        </bitlbee-setting>
     1112
    10621113        <bitlbee-setting name="simulate_netsplit" type="boolean" scope="global">
    10631114                <default>true</default>
    … …  
    11811232
    11821233        <bitlbee-setting name="voice_buddies" type="string" scope="global">
    1183                 <default>trusted</default>
    1184                 <possible-values>encrypted, trusted, notaway, false</possible-values>
     1234                <default>notaway</default>
     1235                <possible-values>encrypted, trusted, notaway, online, false</possible-values>
    11851236
    11861237                <description>
    … …  
    11901241                       
    11911242                        <para>
    1192                                 If "false", the flag is never set. On "notaway", the flag is removed for users marked as "away" and set for all others. On "encrypted", the flag is set for users with whom we have an encrypted connection. On "trusted", it is set only for encrypted connections using a trusted key.
     1243                                If "false", the flag is never set. On "notaway", the flag is removed for users marked as "away" and set for all others. On "encrypted", the flag is set for users with whom we have an encrypted connection. On "trusted", it is set only for encrypted connections using a trusted key. On "online", the flag is set whenever the user is online; only meaningful in conjunction with "show_offline".
    11931244                        </para>
    11941245                </description>
Note: See TracChangeset for help on using the changeset viewer.