Changed: 1c1,23
nrqkav haudegbsv jponzsh uxyonlb pcbg favkqgme citj
The 0.3.6 series is primarily to be noted as a major change in the database structure. Previously nick registration data, channel founders/successors, channel access data, and other things as well, were indexed by nick. The new structure indexes them by a unique nickreg.id. This makes the changing of the root-nick simpler, and should also speed up lookups in many cases.
Further to be noted is the addition of a new generic table, nicktext. It allows many more 'random' features like AUTH, GREET, etc w/o having to create a new table for each. Theoretically many features could be moved into nicktext, and a chantext table is planned.
0.3.6 and 0.3.6.1 were internal development/testing releases.
* chanserv's register: pass and desc are now optional
* cs unban: able to specify persons other than yourself
* /ns alist, info, glist allow multiple nicks to be requested
* ns auth and cs auth
** Proper helpfiles for CS AUTH not written yet
** working ns set auth,
* NS SET GREET,
* NS SET UMODES (a kinda mlock thing for umodes)
** Does not allow oper-specific modes, nor umode +r
* NS SIDENTIFY
** identify and change to that nick in one cmd
*** Will NOT automatically GHOST or RECOVER
*** Will NOT allow you to collide another user.
** mostly useful for nicks with PROTECT HIGH
* OS LONERS
** Find users in zero channels. List, message, kill/kline
* SecurityBot TKL
** List, and delete, according to patterns.
Further to be noted is the addition of a new generic table, nicktext. It allows many more 'random' features like AUTH, GREET, etc w/o having to create a new table for each. Theoretically many features could be moved into nicktext, and a chantext table is planned.
0.3.6 and 0.3.6.1 were internal development/testing releases.
* chanserv's register: pass and desc are now optional
* cs unban: able to specify persons other than yourself
* /ns alist, info, glist allow multiple nicks to be requested
* ns auth and cs auth
** Proper helpfiles for CS AUTH not written yet
** working ns set auth,
* NS SET GREET,
* NS SET UMODES (a kinda mlock thing for umodes)
** Does not allow oper-specific modes, nor umode +r
* NS SIDENTIFY
** identify and change to that nick in one cmd
*** Will NOT automatically GHOST or RECOVER
*** Will NOT allow you to collide another user.
** mostly useful for nicks with PROTECT HIGH
* OS LONERS
** Find users in zero channels. List, message, kill/kline
* SecurityBot TKL
** List, and delete, according to patterns.
The 0.3.6 series is primarily to be noted as a major change in the database structure. Previously nick registration data, channel founders/successors, channel access data, and other things as well, were indexed by nick. The new structure indexes them by a unique nickreg.id. This makes the changing of the root-nick simpler, and should also speed up lookups in many cases. Further to be noted is the addition of a new generic table, nicktext. It allows many more 'random' features like AUTH, GREET, etc w/o having to create a new table for each. Theoretically many features could be moved into nicktext, and a chantext table is planned.
0.3.6 and 0.3.6.1 were internal development/testing releases.
- chanserv's register: pass and desc are now optional
- cs unban: able to specify persons other than yourself
- /ns alist, info, glist allow multiple nicks to be requested
- ns auth and cs auth
- Proper helpfiles for CS AUTH not written yet
- working ns set auth,
- NS SET GREET,
- NS SET UMODES (a kinda mlock thing for umodes)
- Does not allow oper-specific modes, nor umode +r
- NS SIDENTIFY
- identify and change to that nick in one cmd
- Will NOT automatically GHOST or RECOVER
- Will NOT allow you to collide another user.
- mostly useful for nicks with PROTECT HIGH
- identify and change to that nick in one cmd
- OS LONERS
- Find users in zero channels. List, message, kill/kline
- SecurityBot TKL
- List, and delete, according to patterns.
