]> jfr.im git - irc/freenode/web-7.0.git/blob - content/kb/using/registration.md
add knowledge base content
[irc/freenode/web-7.0.git] / content / kb / using / registration.md
1 Title: Nickname Registration
2 ---
3 Your nick is how people on freenode know you. If you register it, you'll be able to use the same nick over and over. If you don't register, someone else may end
4 up registering the nick you want. If you register and use the same nick, people will begin to know you by reputation.
5
6 If a channel is set to mode +r, you won't be able to join it unless you are registered and identified to NickServ. If you try to join, you might be forwarded to
7 a different channel. If a channel is set to quiet unregistered users (mode `+q $~a`), you won't be able to speak while on that channel unless you are registered
8 and identified. Both of these modes are used by some channels to reduce channel harassment and abuse.
9
10 Nickname Setup
11 ==============
12
13 The following steps are the recommended method to register and set up a new freenode account. If you have questions or doubts about the process, a member of
14 staff will be happy to discuss it and answer any questions you may have.
15
16 1. Select a permanent, master nickname. If the nickname you want is registered but has expired, just ask a staffer and in most cases, we will be happy to drop
17 it for you. Please avoid using the name of a community project or trademarked entity, to avoid conflicts. Write down your password and be sure to keep the
18 sheet of paper in a safe place.
19
20 2. Register your IRC nick:
21
22 /msg NickServ REGISTER password youremail@example.com
23
24 Replace password with a secure, unguessable password that you keep secret.
25
26 The email address that you select will not be given out by staff, and is mainly used to allow us to help you recover the account in the event that you forget
27 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
28 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
29 after about 24 hours.
30
31 3. It's useful, but not required, to have an alternate nick grouped to your account. For example, if your primary nick is foo:
32
33 /nick foo_
34
35 then identify to your primary account:
36
37 /msg NickServ IDENTIFY foo password
38
39 and finally, group the new nick to your account
40
41 /msg NickServ GROUP
42
43 We prefer you to use just one account, and group nicks to it as described above, rather than registering for multiple accounts. Grouping nicks in this way
44 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
45 run a bot. You should register a separate account for your bot.
46
47 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
48 without being identified to NickServ. The easiest approach is to specify your NickServ password as a server password. If your client supports server
49 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,
50 regardless of the nickname you are using when you connect. For example: /connect chat.freenode.net 6667 mquin:uwhY8wgzWw22-zXs.M39p
51
52
53 Logging In
54 ==========
55
56 You'll need to log in to your nickname each time you reconnect to freenode.
57
58 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
59 the form `<account>:<password>`, as a server password and they will be forwarded to NickServ when you finish connecting.
60
61 Nickname Expiry
62 ===============
63
64 Registered nicknames and accounts will expire if they're not used for a long time, after which they'll be available for another user to take over. See our
65 [policies](/pages/policies) for details of when this occurs.
66
67 While nicknames and accounts do not automatically get deleted when they expire -- only when another user requests to take over the registration -- we do
68 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
69 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.