From f8d5fa9b1cc85f1565d475ceedb6ced9652351b7 Mon Sep 17 00:00:00 2001 From: Emmanuel Gil Peyrot Date: Sat, 8 Oct 2016 22:40:03 +0100 Subject: Remove the resource option from the configuration. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It’s considered bad practice nowadays to force a specific resource, it can lead to presence leaks or reconnection loops so should be avoided. Moreover this was already possible in the jid option, by setting it to user@domain/resource, setting it would append it a second time in that case. --- doc/source/configuration.rst | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) (limited to 'doc/source/configuration.rst') diff --git a/doc/source/configuration.rst b/doc/source/configuration.rst index 4a1af1eb..131915c9 100644 --- a/doc/source/configuration.rst +++ b/doc/source/configuration.rst @@ -110,7 +110,7 @@ Options related to account configuration, nickname… account on a server. This is optional and useful only for some features, like room administration or nickname registration. The :term:`server` option will be ignored if you specify a JID (Jabber id) - It should be in the form nickname@server.tld + It should be in the form nickname@server.tld or nickname@server.tld/resource custom_host @@ -172,14 +172,6 @@ Options related to account configuration, nickname… through SASL External. If set, :term:`keyfile` **MUST** be set as well in order to login. - resource - - **Default value:** ``[empty]`` - - The resource you will use. If it's empty, your resource will be chosen - (most likely randomly) by the server. It is not recommended to use a - resource that is easy to guess, because it can lead to presence leak. - rooms **Default value:** ``[empty]`` -- cgit v1.2.3