Changes in doc/user-guide/commands.xml [f9110b4:8eb0b76]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/commands.xml
rf9110b4 r8eb0b76 484 484 </bitlbee-setting> 485 485 486 <bitlbee-setting name="base_url" type="string" scope="account"> 487 <default>http://twitter.com</default> 488 489 <description> 490 <para> 491 There are more services that understand the Twitter API than just Twitter.com. BitlBee can connect to all Twitter API implementations. 492 </para> 493 494 <para> 495 For example, set this setting to <emphasis>http://identi.ca/api</emphasis> to use Identi.ca. 496 </para> 497 498 <para> 499 Keep two things in mind: When not using Twitter, you <emphasis>must</emphasis> also disable the <emphasis>oauth</emphasis> setting as it currently only works with Twitter. If you're still having issues, make sure there is <emphasis>no</emphasis> slash at the end of the URL you enter here. 500 </para> 501 </description> 502 </bitlbee-setting> 503 486 504 <bitlbee-setting name="buddy_sendbuffer" type="boolean" scope="global"> 487 505 <default>false</default> … … 1006 1024 </bitlbee-setting> 1007 1025 1026 <bitlbee-setting name="user_agent" type="string" scope="account"> 1027 <default>BitlBee</default> 1028 1029 <description> 1030 <para> 1031 Some Jabber servers are configured to only allow a few (or even just one) kinds of XMPP clients to connect to them. 1032 </para> 1033 1034 <para> 1035 You can change this setting to make BitlBee present itself as a different client, so that you can still connect to these servers. 1036 </para> 1037 </description> 1038 </bitlbee-setting> 1039 1008 1040 <bitlbee-setting name="web_aware" type="string" scope="account"> 1009 1041 <default>false</default>
Note: See TracChangeset
for help on using the changeset viewer.