content/news/2008-05-31-new-services-nicknames-and-accounts.md

   1 ---
   2 author: skenmy
   3 date: 2008-05-31 17:56:35+00:00
   4 slug: new-services-nicknames-and-accounts
   5 title: New Services: Nicknames and Accounts
   6 category: freenode
   7 category: technical
   8 imported: yes
   9 ---
  10 We've noticed a lot of people who are confused (and rightly so!) about the new nickname system - particularly the way that nickname grouping has changed. Hopefully this blog post will clear some of it up.
  11
  12 # Nicknames and Accounts
  13
  14 freenode now uses a system of ownership that is different to the old nicknames system. Now, when you register a _nickname_ for the first time, that _nickname_ becomes the primary _nickname_ on your _account_ (which has the same name). An example:
  15
  16 > **User1** vists Freenode for the first time. She registers by using the
  17 > command:
  18 >
  19 > > /msg NickServ REGISTER myshinypass my@shiny.email
  20 >
  21 > **User1 **now has an _account_. freenode services have automatically assigned
  22 > the _nickname_ **User1** to the _account_ **User1**. **User1** is now
  23 > happy.
  24
  25
  26 So, _nicknames_ are now assigned to your _account_. But what does this actually mean, practically?
  27
  28 # Identification
  29
  30 When you identify:
  31
  32
  33 > /msg NickServ IDENTIFY &lt;password&gt;
  34
  35
  36 freenode services will try and identify you to your _account_.  It does this by taking your _nickname_, and looking it up in the database - to find the _account_ associated with it. Let's go back to User1 for a little demonstration:
  37
  38
  39 > **User1** returns to freenode. She identifies using the command:
  40 >
  41 > > /msg NickServ IDENTIFY myshinypass
  42 >
  43 >
  44 > freenode services finds an _account_ (**User1**) with the same _nickname_ as
  45 > her (**User1**), and so identifies her succesfully.
  46
  47
  48 But what happens when you try and identify with a different nickname?
  49
  50
  51 > **User1 **connects to freenode, but her client decides to connect with the
  52 > _nickname_ **User12.** She tries to identify using the command:
  53 >
  54 > > /msg NickServ IDENTIFY myshinypass
  55 >
  56 > freenode services tries to look up an account called **User12** (as this is
  57 > her current nickname). This nickname is unregistered, and so does not have an
  58 > account associated with it. The identification fails, and she is not logged
  59 > in.
  60
  61
  62 With the new accounts system, there is a command that allows you to identify to your account from any nickname!
  63
  64
  65 > **User1 **connects to freenode, but her client decides to connect with the
  66 > _nickname_ **User12.** She can identify using the command:
  67 >
  68 > > /msg NickServ IDENTIFY User1 myshinypass
  69 >
  70 > freenode services will now look for an _account_ named **User1**, and log her
  71 > into that. Since she already registered this, the identification succeeds.
  72
  73
  74 However, this isn't ideal, as she is now logged in, but is using an unregistered _nickname_. She may want to consider GROUPing the _nickname_.
  75
  76
  77 # Grouping
  78
  79 With the new system, GROUP basically means to add another _nickname_ to your _account_. **User1** is fed up of being connected as **User12** and using an unregistered _nickname_, so she has decided to GROUP the _nickname_ to her existing _account_.
  80
  81 There are two ways to go about this:
  82
  83
  84 > **User1 **connects to freenode, but her client decides to connect with the
  85 > _nickname_ **User12.** She can identify using the command:
  86 >
  87 > > /msg NickServ IDENTIFY User1 myshinypass
  88 >
  89 >
  90 > freenode services will now look for an _account_ named **User1**, and log her
  91 > into that. Since she already registered this, the identification succeeds.
  92 > She can now GROUP the _nickname_ (**User12**) to her _account_ (**User1**) by
  93 > typing:
  94 >
  95 > > /msg NickServ GROUP
  96 >
  97 >
  98 > The command takes the current _nickname_, and adds it to the currently logged
  99 > in _account_. She can now, in the future, identify using the command:
 100 >
 101 > > /msg NickServ IDENTIFY myshinypass
 102 >
 103 >
 104 > when connected as **User12**.
 105
 106
 107 Or, she can do this:
 108
 109
 110 > **User1** connects to freenode. She identifies using the command:
 111 >
 112 > > /msg NickServ IDENTIFY myshinypass
 113 >
 114 >
 115 > freenode services finds an _account_ (**User1**) with the same _nickname_ as her (**User1**), and so identifies her succesfully. She can now change her _nickname_:
 116 >
 117 > > /nick User12
 118 >
 119 >
 120 > And GROUP her new _nickname_, as freenode services does not log her out of her _account_ when she changes _nickname_.
 121 >
 122 > > /msg NickServ GROUP
 123 >
 124 >
 125 > The command takes the current _nickname_, and adds it to the currently logged in _account_. She can now, in the future, identify using the command:
 126 >
 127 > > /msg NickServ IDENTIFY myshinypass
 128 >
 129 >
 130 > when connected as **User12**.
 131
 132
 133 # Conclusion
 134
 135 So, to wrap up, freenode now allows you to register an account, to which you add nicknames as explained above. That's not an easy concept to grasp if you are used to the old system, and if you have any questions, feel free to drop into #freenode and ask away!