[irc/freenode/web-7.0.git] / content / news / 2008-05-31-new-services-nicknames-and-accounts.md

author: skenmy
date: 2008-05-31 17:56:35+00:00
slug: new-services-nicknames-and-accounts
title: New Services: Nicknames and Accounts
category: freenode
category: technical
---
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.

# Nicknames and Accounts

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:

> **User1** vists Freenode for the first time. She registers by using the
> command:
>
> > /msg NickServ REGISTER myshinypass my@shiny.email
>
> **User1 **now has an _account_. freenode services have automatically assigned
> the _nickname_ **User1** to the _account_ **User1**. **User1** is now
> happy.


So, _nicknames_ are now assigned to your _account_. But what does this actually mean, practically?

# Identification

When you identify:


> /msg NickServ IDENTIFY &lt;password&gt;


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:


> **User1** returns to freenode. She identifies using the command:
>
> > /msg NickServ IDENTIFY myshinypass
>
>
> freenode services finds an _account_ (**User1**) with the same _nickname_ as
> her (**User1**), and so identifies her succesfully.


But what happens when you try and identify with a different nickname?


> **User1 **connects to freenode, but her client decides to connect with the
> _nickname_ **User12.** She tries to identify using the command:
>
> > /msg NickServ IDENTIFY myshinypass
>
> freenode services tries to look up an account called **User12** (as this is
> her current nickname). This nickname is unregistered, and so does not have an
> account associated with it. The identification fails, and she is not logged
> in.


With the new accounts system, there is a command that allows you to identify to your account from any nickname!


> **User1 **connects to freenode, but her client decides to connect with the
> _nickname_ **User12.** She can identify using the command:
>
> > /msg NickServ IDENTIFY User1 myshinypass
>
> freenode services will now look for an _account_ named **User1**, and log her
> into that. Since she already registered this, the identification succeeds.


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_.


# Grouping

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_.

There are two ways to go about this:


> **User1 **connects to freenode, but her client decides to connect with the
> _nickname_ **User12.** She can identify using the command:
>
> > /msg NickServ IDENTIFY User1 myshinypass
>
>
> freenode services will now look for an _account_ named **User1**, and log her
> into that. Since she already registered this, the identification succeeds.
> She can now GROUP the _nickname_ (**User12**) to her _account_ (**User1**) by
> typing:
>
> > /msg NickServ GROUP
>
>
> 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:
>
> > /msg NickServ IDENTIFY myshinypass
>
>
> when connected as **User12**.


Or, she can do this:


> **User1** connects to freenode. She identifies using the command:
>
> > /msg NickServ IDENTIFY myshinypass
>
>
> freenode services finds an _account_ (**User1**) with the same _nickname_ as her (**User1**), and so identifies her succesfully. She can now change her _nickname_:
>
> > /nick User12
>
>
> And GROUP her new _nickname_, as freenode services does not log her out of her _account_ when she changes _nickname_.
>
> > /msg NickServ GROUP
>
>
> 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:
>
> > /msg NickServ IDENTIFY myshinypass
>
>
> when connected as **User12**.


# Conclusion

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!
Commit	Line	Data
849bdd6f SB	1	author: skenmy
	2	date: 2008-05-31 17:56:35+00:00
	3	slug: new-services-nicknames-and-accounts
eeb00e73	4	title: New Services: Nicknames and Accounts
c5191f36 EK	5	category: freenode
c5191f36 EK	6	category: technical
849bdd6f	7	---
849bdd6f	8	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.
34876803	9
951245ff	10	# Nicknames and Accounts
34876803	11
849bdd6f SB	12	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:
849bdd6f SB	13
951245ff EK	14	> User1 vists Freenode for the first time. She registers by using the
	15	> command:
	16	>
	17	> > /msg NickServ REGISTER myshinypass my@shiny.email
	18	>
	19	> User1 now has an _account_. freenode services have automatically assigned
	20	> the _nickname_ User1 to the _account_ User1. User1 is now
	21	> happy.
849bdd6f SB	22
	23
	24	So, _nicknames_ are now assigned to your _account_. But what does this actually mean, practically?
34876803	25
951245ff	26	# Identification
34876803	27
849bdd6f SB	28	When you identify:
	29
	30
951245ff	31	> /msg NickServ IDENTIFY <password>
849bdd6f SB	32
	33
	34	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:
	35
	36
951245ff EK	37	> User1 returns to freenode. She identifies using the command:
	38	>
	39	> > /msg NickServ IDENTIFY myshinypass
	40	>
	41	>
	42	> freenode services finds an _account_ (User1) with the same _nickname_ as
	43	> her (User1), and so identifies her succesfully.
849bdd6f SB	44
	45
	46	But what happens when you try and identify with a different nickname?
	47
	48
951245ff EK	49	> User1 connects to freenode, but her client decides to connect with the
	50	> _nickname_ User12. She tries to identify using the command:
	51	>
	52	> > /msg NickServ IDENTIFY myshinypass
	53	>
	54	> freenode services tries to look up an account called User12 (as this is
	55	> her current nickname). This nickname is unregistered, and so does not have an
	56	> account associated with it. The identification fails, and she is not logged
	57	> in.
849bdd6f SB	58
	59
	60	With the new accounts system, there is a command that allows you to identify to your account from any nickname!
	61
	62
951245ff EK	63	> User1 connects to freenode, but her client decides to connect with the
	64	> _nickname_ User12. She can identify using the command:
	65	>
	66	> > /msg NickServ IDENTIFY User1 myshinypass
	67	>
	68	> freenode services will now look for an _account_ named User1, and log her
	69	> into that. Since she already registered this, the identification succeeds.
849bdd6f SB	70
	71
	72	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_.
34876803	73
951245ff EK	74
951245ff EK	75	# Grouping
34876803	76
849bdd6f	77	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_.
34876803	78
849bdd6f SB	79	There are two ways to go about this:
	80
	81
951245ff EK	82	> User1 connects to freenode, but her client decides to connect with the
	83	> _nickname_ User12. She can identify using the command:
	84	>
	85	> > /msg NickServ IDENTIFY User1 myshinypass
	86	>
	87	>
	88	> freenode services will now look for an _account_ named User1, and log her
	89	> into that. Since she already registered this, the identification succeeds.
	90	> She can now GROUP the _nickname_ (User12) to her _account_ (User1) by
	91	> typing:
	92	>
	93	> > /msg NickServ GROUP
	94	>
	95	>
	96	> The command takes the current _nickname_, and adds it to the currently logged
	97	> in _account_. She can now, in the future, identify using the command:
	98	>
	99	> > /msg NickServ IDENTIFY myshinypass
	100	>
	101	>
	102	> when connected as User12.
849bdd6f SB	103
	104
	105	Or, she can do this:
	106
	107
951245ff EK	108	> User1 connects to freenode. She identifies using the command:
	109	>
	110	> > /msg NickServ IDENTIFY myshinypass
	111	>
	112	>
	113	> freenode services finds an _account_ (User1) with the same _nickname_ as her (User1), and so identifies her succesfully. She can now change her _nickname_:
	114	>
	115	> > /nick User12
	116	>
	117	>
	118	> And GROUP her new _nickname_, as freenode services does not log her out of her _account_ when she changes _nickname_.
	119	>
	120	> > /msg NickServ GROUP
	121	>
	122	>
	123	> 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:
	124	>
	125	> > /msg NickServ IDENTIFY myshinypass
	126	>
	127	>
	128	> when connected as User12.
	129
	130
	131	# Conclusion
34876803	132
849bdd6f	133	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!