- Timestamp:
- 2010-04-24T17:02:07Z (15 years ago)
- Branches:
- master
- Children:
- c521362
- Parents:
- b5b40ff (diff), f1b7711 (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. - Location:
- doc
- Files:
-
- 2 edited
-
CHANGES (modified) (2 diffs)
-
user-guide/commands.xml (modified) (7 diffs)
Legend:
- Unmodified
- Added
- Removed
-
doc/CHANGES
rb5b40ff rae3dc99 3 3 4 4 http://bugs.bitlbee.org/bitlbee/timeline?daysback=90&changeset=on 5 6 Version 1.2.6a: 7 - Fixed a typo that renders the Twitter groupchat mode unusable. A last- 8 minute change that came a few minutes late. 9 10 Finished 19 Apr 2010 11 12 Version 1.2.6: 13 - Native (very basic) support for Twitter, implemented by Geert Mulders. 14 Currently supported are posting tweets, reading the ones of people you 15 follow, and sending (not yet receiving!) direct messages. 16 - Fixed format of status messages in /WHOIS to improve IRC client 17 compatibility. 18 - Show timestamps of offline messages/channel backlogs. 19 - Allow saving MSN display names locally since sometimes this stuff breaks 20 server-side. (Use the local_display_name per-account setting.) 21 - Suppress empty "Headline:" messages for certain new XMPP broadcast 22 messages. 23 - Better handling of XMPP contacts with multiple resources on-line. Default 24 behaviour now is to write to wherever the last message came from, or to 25 the bare JID (usually becomes a broadcast) if there wasn't any recent msg. 26 - Added a switchboard_keepalives setting which should solve some issues with 27 talking to offline MSN contacts. (Although full support for offline 28 messages is not ready yet!) 29 - The usual misc. bug fixes. 30 31 Finished 19 Apr 2010 5 32 6 33 Version 1.2.5: … … 23 50 the main client). 24 51 25 Fi xed 17 Mar 201052 Finished 17 Mar 2010 26 53 27 54 Version 1.2.4: -
doc/user-guide/commands.xml
rb5b40ff rae3dc99 21 21 <description> 22 22 <para> 23 Adds an account on the given server with the specified protocol, username and password to the account list. Supported protocols right now are: Jabber, MSN, OSCAR (AIM/ICQ) and Yahoo. For more information about adding an account, see <emphasis>help account add <protocol></emphasis>.23 Adds an account on the given server with the specified protocol, username and password to the account list. Supported protocols right now are: Jabber, MSN, OSCAR (AIM/ICQ), Yahoo and Twitter. For more information about adding an account, see <emphasis>help account add <protocol></emphasis>. 24 24 </para> 25 25 </description> … … 63 63 </ircexample> 64 64 </bitlbee-command> 65 66 <bitlbee-command name="twitter"> 67 <syntax>account add twitter <handle> <password></syntax> 68 69 <description> 70 <para> 71 This module gives you simple access to Twitter. Although it uses the Twitter API, only Twitter itself is supported at the moment. 72 </para> 73 74 <para> 75 By default all your Twitter contacts will come from a contact called twitter_(yourusername). You can change this behaviour using the <emphasis>mode</emphasis> setting (see <emphasis>help set mode</emphasis>). 76 </para> 77 78 <para> 79 To send tweets yourself, send them to the twitter_(yourusername) contact, or just write in the groupchat channel if you enabled that option. 80 </para> 81 </description> 82 </bitlbee-command> 65 83 66 84 <bitlbee-command name="yahoo"> … … 401 419 402 420 <bitlbee-setting name="auto_reconnect" type="boolean" scope="both"> 403 <default> false</default>421 <default>true</default> 404 422 405 423 <description> … … 556 574 <para> 557 575 With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name". 576 </para> 577 </description> 578 </bitlbee-setting> 579 580 <bitlbee-setting name="display_timestamps" type="boolean" scope="global"> 581 <default>true</default> 582 583 <description> 584 <para> 585 When incoming messages are old (i.e. offline messages and channel backlogs), BitlBee will prepend them with a timestamp. If you find them ugly or useless, you can use this setting to hide them. 558 586 </para> 559 587 </description> … … 609 637 </bitlbee-setting> 610 638 639 <bitlbee-setting name="local_display_name" type="boolean" scope="account"> 640 <default>false</default> 641 642 <description> 643 <para> 644 Mostly meant to work around a bug in MSN servers (forgetting the display name set by the user), this setting tells BitlBee to store your display name locally and set this name on the MSN servers when connecting. 645 </para> 646 </description> 647 648 </bitlbee-setting> 649 611 650 <bitlbee-setting name="mail_notifications" type="boolean" scope="account"> 612 651 <default>false</default> … … 615 654 <para> 616 655 Some protocols (MSN, Yahoo!) can notify via IM about new e-mail. Since most people use their Hotmail/Yahoo! addresses as a spam-box, this is disabled default. If you want these notifications, you can enable this setting. 656 </para> 657 </description> 658 659 </bitlbee-setting> 660 661 <bitlbee-setting name="mode" type="string" scope="account"> 662 <possible-values>one, many, chat</possible-values> 663 <default>one</default> 664 665 <description> 666 <para> 667 By default, everything from the Twitter module will come from one nick, twitter_(yourusername). If you prefer to have individual nicks for everyone, you can set this setting to "many" instead. 668 </para> 669 670 <para> 671 If you prefer to have all your Twitter things in a separate channel, you can set this setting to "chat". 672 </para> 673 674 <para> 675 In the last two modes, you can send direct messages by /msg'ing your contacts directly. Note, however, that incoming DMs are not fetched yet. 617 676 </para> 618 677 </description> … … 824 883 <para> 825 884 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. 885 </para> 886 </description> 887 </bitlbee-setting> 888 889 <bitlbee-setting name="switchboard_keepalives" type="boolean" scope="account"> 890 <default>false</default> 891 892 <description> 893 <para> 894 Turn on this flag if you have difficulties talking to offline/invisible contacts. 895 </para> 896 897 <para> 898 With this setting enabled, BitlBee will send keepalives to MSN switchboards with offline/invisible contacts every twenty seconds. This should keep the server and client on the other side from shutting it down. 899 </para> 900 901 <para> 902 This is useful because BitlBee doesn't support MSN offline messages yet and the MSN servers won't let the user reopen switchboards to offline users. Once offline messaging is supported, this flag might be removed. 903 </para> 904 </description> 905 </bitlbee-setting> 906 907 <bitlbee-setting name="timezone" type="string" scope="global"> 908 <default>local</default> 909 <possible-values>local, utc, gmt, timezone-spec</possible-values> 910 911 <description> 912 <para> 913 If message timestamps are available for offline messages or chatroom backlogs, BitlBee will display them as part of the message. By default it will use the local timezone. If you're not in the same timezone as the BitlBee server, you can adjust the timestamps using this setting. 914 </para> 915 916 <para> 917 Values local/utc/gmt should be self-explanatory. timezone-spec is a time offset in hours:minutes, for example: -8 for Pacific Standard Time, +2 for Central European Summer Time, +5:30 for Indian Standard Time. 826 918 </para> 827 919 </description>
Note: See TracChangeset
for help on using the changeset viewer.
