Keep conversations in foreground

doc/EN/usage.org

 # HexChat should not use the same circuit/exit server as other Tor applications.
 # Otherwise activity in different applications could be correlated to the same
 # pseudonym. There is a way to prevent that.
-# It is called stream isolation. We use IsolateSOCKSAuth, 
+# It is called stream isolation. We use IsolateSOCKSAuth,
 # see https://www.torproject.org/docs/tor-manual-dev.html.en
 # The password is actually not required, but it does not hurt either.
 # Will probable not hurt on Tor 0.2.2 and below.
 # /set irc_hide_version ON
 # /set identd OFF <-- NOT working on all HexChat-based IRC software.
 # But still highly suggested to include & use it.
-# Probable not needed on UNIX, source: http://xchat.org/faq/#q21 
+# Probable not needed on UNIX, source: http://xchat.org/faq/#q21
 dcc_auto_chat = 0
 dcc_auto_resume = 0
 dcc_auto_send = 0
 # -> Quit: <Deleted everything!>
 # -> Leave channel: <Deleted everything!>
 # -> Away: <Deleted everything!>
-away_reason = 
-irc_part_reason = 
-irc_quit_reason = 
+away_reason =
+irc_part_reason =
+irc_quit_reason =
 
 # By default, HexChat based IRC software uses your platform OS(Operating System)s
 # login user name as your nickname, user name, real name.  To prevent leaking
 
 Add an account and enter your Jabber/XMPP ID and password.
 
-From the menu select *Settings* then *Expert Settings*. Select *Connect via Tor* and depending on your situation you might also want to select *Don't save encrypted messages*.
+From the menu select *Settings* then *Expert Settings*. Select *Connect via Tor* and depending on your situation you might also want to select *Don't save encrypted messages*. Also within expert settings select *Keep in foreground*. This will enable you to still receive notifications when your device is in standby mode with the screen turned off.
 
 From the menu select *Manage accounts* and add a new account.
 
 Port:      5222
 #+END_SRC
 
-Then select *Next*. When chatting you can use the lock icon to encrypt your conversation. It's also going through Tor, so passive surveillance of the metadata should not be easy for an adversary.
+Then select *Next*. When chatting you can use the lock icon to encrypt your conversation. OMEMO is the recommended type of encryption. It's also going through Tor, so passive surveillance of the metadata should not be easy for an adversary.
 ** Tox
 Tox is an encrypted peer-to-peer messaging system and so should work without Freedombone. It uses a system of nodes which act as a sort of directory service allowing users to find and connect to each other. The Tox node ID on the Freedombone can be found within the README within your home directory. If you have other users connect to your node then you will be able to continue chatting even when no other nodes are available.
 *** Using the Toxic client
 (require 'socks)
 (require 'tls)
 (setq socks-server (list "Tor socks" "localhost" 9050 5))
-#+end_src 
+#+end_src
 
 And ensure that the Tor daemon is installed: