]> jfr.im git - irc/freenode/web-7.0.git/blob - content/news/2008-05-29-services-migration.md
test nowrap lines
[irc/freenode/web-7.0.git] / content / news / 2008-05-29-services-migration.md
1 author: Martinp23
2 date: 2008-05-29 15:06:27+00:00
3 slug: services-migration
4 title: Services Migration
5 categories:
6 - freenode
7 - projects
8 - technical
9 ---
10
11 The time has come for freenode to migrate from our old, legacy services package to a much newer, actively maintained package known as [Atheme](http://www.atheme.net/), developed by the [Atheme Project](http://www.atheme.org/). Although we, with the help of the Atheme developers, have tried to make the migration process as painless as possible, there are still a few interface differences that you will need to be aware of. This guide, prepared by tomaw, will attempt to walk you through the main changes, grouped by service.
12
13
14 ## NickServ
15
16
17
18
19
20
21 * NickServ will now require a valid, verified email address to register new nicks. Because of this the registration command has changed to
22
23
24 /msg NickServ REGISTER <password> <email address>
25
26
27 You will the receive a confirmation email with instructions on how to confirm your account registration. Accounts that have been migrated from theia that did not have an email address set will find that their address is set to 'nomail'. **These users should set an email address as soon as possible.**
28
29
30 * New NickServ accounts that are registered but not confirmed will be **automatically** dropped after 24 hours.
31
32
33 * What was Nick Linking has now been replaced with Nick Grouping. This means that you have just one account (including one password, one email address etc.) but potentially multiple Nicks associated with that account. For more information please issue the following command:
34
35
36 /msg NickServ HELP GROUP
37
38
39 Migrated accounts will have the password associated to the master nick, but will have the first valid email address found when searching all linked nicks.
40
41
42 * SET UNFILTERED has been removed and the global block on messages from users that have not identified to NickServ has been removed. This was only ever intended to be a temporary measure to combat spam and we're hopeful that we can deal with those events in different, less intrusive ways. UMODE +E remains an alternative for any users who wish to block such messages.
43
44
45 * SET GSM, PHONE, and the like have been removed and replaced with a SET PROPERTY feature. For more information, see:
46
47
48 /msg NickServ HELP SET PROPERTY
49
50
51
52
53
54 * INFO will no long return a list of channels where you have access. Instead use:
55
56
57 /msg NickServ LISTCHANS
58
59
60
61
62
63 * A new SET ENFORCE feature replaces the un-used SET KILL feature. For details, see
64
65
66 /msg NickServ HELP SET ENFORCE
67
68
69
70
71
72
73
74 ## ChanServ
75
76
77
78
79
80
81 * Channel access is now controlled by a series of flags, rather than levels. This will allow channel owners and Group Contacts to better control the access they grant users, and to see more clearly what access those users will have. Channel Access now also includes a powerful templating system, making it easier to manage large and complicated access lists. For more information on these features, please see:
82
83
84 /msg ChanServ HELP FLAGS
85
86
87
88
89 /msg ChanServ HELP TEMPLATE
90
91
92
93
94 /msg ChanServ HELP ACCESS
95
96
97
98
99
100 * Channel access can now be manipulated using two different commands.
101
102
103 /msg ChanServ ACCESS #channel
104
105
106 behaves similarly to our previous services, but the standard Atheme command is to use
107
108
109 /msg ChanServ FLAGS
110
111
112 Note that viewing FLAGS requires you to have flag +A on the channel in question, but ACCESS does not. This can be useful if you're trying to locate channel operators.
113
114
115 * ChanServ can no longer be used to OP or VOICE multiple users, though it is still possibly to OP/VOICE individual users:
116
117
118 /msg ChanServ OP #channel nick
119
120
121
122
123
124 * A new RECOVER command is now available, which can be used by the founder to regain control of a channel which has been "taken over".
125
126
127 * Channel passwords are no longer used for registration as all channel access is control by the access flags.
128
129
130 * LIST *pattern* has been replaced by a new service called ALIS. See below for details.
131
132
133
134
135 ## ALIS
136
137
138
139
140
141
142 * ALIS provides a more useful channel list facility than what was previously available. It will list matching channels, but will filter out channels that are not currently in use. Its use is similar to the functionality that was previously built into ChanServ:
143
144
145 /msg ALIS LIST #freenode-*
146
147
148
149
150
151
152
153 ## MemoServ
154
155
156
157
158
159
160 * Memos can now be replied to and forwarded to other users
161
162
163 * Optional email forwarding to your registered email address. To enable this feature, issue the following command:
164
165
166 /msg NickServ SET EMAILMEMOS ON
167
168
169
170
171
172 Hopefully that covers most of the differences that you will come across during day to day life on freenode. Of course, if you have any questions, suggestions or comments, please feel free to drop by [#freenode](irc://irc.freenode.net/freenode), email support (at) freenode (dot) net or message a member of staff.