projects / irc / freenode / web-7.0.git / blame
| Commit | Line | Data |
|---|---|---|
| c5293e15 | 1 | --- |
| 849bdd6f SB |
2 | author: christel |
| 3 | date: 2009-01-05 13:34:32+00:00 | |
| 4 | slug: nickserv-access-module-loaded | |
| 5 | title: Nickserv Access Module Loaded. | |
| c5191f36 EK |
6 | category: freenode |
| 7 | category: technical | |
| df8e5765 | 8 | imported: yes |
| 3406dcfa | 9 | robots: noindex |
| 849bdd6f | 10 | --- |
| 849bdd6f | 11 | We recently added support for NickServ's ACCESS command to freenode's services. This allows you to define a list of hostmasks from which nickserv will recognise you before you have identified. Logging in as normal is still required, but matching an entry on this list will prevent NickServ from changing your nick if ENFORCE is enabled. |
| 34876803 | 12 | |
| 849bdd6f | 13 | For more detailed information, see NickServ's help topic: |
| 34876803 | 14 | |
| 849bdd6f | 15 | /msg NickServ HELP ACCESS |
| 34876803 | 16 | |
| 849bdd6f | 17 | There is one caveat to this feature: if you match an entry on your nickname's access list, you will not receive notices from NickServ asking you to identify. This, combined with nickname access lists that were migrated from our old theia database and have lain dormant since, may cause some auto-identify scripts to stop functioning. |
| 34876803 | 18 | |
| 849bdd6f | 19 | If you find that this is the case, the simplest workaround is just to remove all entries from your nickname's access list. Use |
| 34876803 | 20 | |
| 849bdd6f | 21 | /msg NickServ ACCESS LIST |
| 34876803 | 22 | |
| 849bdd6f | 23 | to see all entries, and |
| 34876803 | 24 | |
| 849bdd6f | 25 | /msg NickServ ACCESS DEL <hostmask> |
| 34876803 | 26 | |
| 849bdd6f | 27 | to remove them. |