Add instructions for setting modes

[irc/freenode/web-7.0.git] / content / kb / using / registration.md

diff --git a/content/kb/using/registration.md b/content/kb/using/registration.md
index 7bb8bd4352f0ffcbf21e67127309deed13abf86a..66bc664b323c4de68536242434a8320bb8854ce3 100755 (executable)
--- a/content/kb/using/registration.md
+++ b/content/kb/using/registration.md
@@ -27,6 +27,8 @@ staff will be happy to discuss it and answer any questions you may have.
     your password. For this reason, you are required to use a real, non-disposable, email address. Upon registering, you will receive an email with a
     verification command that you will need to run to complete the registration process. Failure to verify the account will cause it to be automatically dropped
     after about 24 hours.
+    
+    We do not recommend sharing your NickServ password with anyone else as this could compromise account security and make it harder for you to recover your account in the future.
 
 3.  It's useful, but not required, to have an alternate nick grouped to your account. For example, if your primary nick is foo:
 
@@ -44,19 +46,15 @@ staff will be happy to discuss it and answer any questions you may have.
     gives you the benefit of having all your nicks covered by the same cloak, should you choose to wear a cloak. The exception to this is where you might want to
     run a bot. You should register a separate account for your bot.
 
-4.  Configure your client to identify itself to NickServ automatically whenever it connects to freenode so that it's less likely you'll connect to the network
-    without being identified to NickServ. The easiest approach is to specify your NickServ password as a server password.  If your client supports server
-    password, please set this up as accountname:password. Make sure to include the colon. This will allow you to identify to your services account on connect,
-    regardless of the nickname you are using when you connect. For example: /connect chat.freenode.net 6667 mquin:uwhY8wgzWw22-zXs.M39p
-
-
 Logging In
 ==========
 
 You'll need to log in to your nickname each time you reconnect to freenode.
 
 The simplest, and most robust, way to do this is to configure [SASL](kb/using/sasl), if your client supports it. If not, you can supply your login details, in
-the form `<account>:<password>`, as a server password and they will be forwarded to NickServ when you finish connecting.
+the form `<account>:<password>`, as a server password and they will be forwarded to NickServ when you finish connecting. For example:
+
+    /connect chat.freenode.net 6667 mquin:uwhY8wgzWw22-zXs.M39p
 
 Nickname Expiry
 ===============
@@ -67,3 +65,4 @@ Registered nicknames and accounts will expire if they're not used for a long tim
 While nicknames and accounts do not automatically get deleted when they expire -- only when another user requests to take over the registration -- we do
 occasionally perform clean-up runs on the services database, in which we will automatically drop all registrations which have been idle for a long time. When we
 do this, we set the threshold for deletion considerably higher than the documented expiry time, to ensure that users close to the limit do not lose out.
+