|
Notes |
|
|
(0006784)
|
|
Konar6
|
|
2013-07-24 08:23
|
|
|
The problem with Doomsseker IRC is more serious regarding halfops - it doesn't support halfops at all. |
|
|
|
(0006790)
|
|
Zalewa
|
|
2013-07-25 17:52
|
|
Well, Doomseeker IRC didn't support halfops because they're not part of the RFC 1459 standard. Anyway, this commit shall fix this.
Update is available through Beta auto-update channel or here:
'http://devbuilds.drdteam.org/doomseeker/ [^]'
I need some feedback:
Are there any other non-standard user modes that add prefix to nickname and are not a part of the standard?
Do any servers allow to prepend more than one mode prefix to user name (for example: "@%+Dusk")?
Doomseeker isn't prepared to handle these situations properly either. |
|
|
|
(0006794)
|
|
Konar6
|
2013-07-25 18:50
(edited on: 2013-07-25 18:54) |
|
Good job.
> Are there any other non-standard user modes that add prefix to nickname and are not a part of the standard?
Not enabled on our network, but some networks may utilize two more prefixes, by standard:
mode char q, prefix ~ - founder (owner) "This channel mode marks a user as the channel founder. A +q user is protected from kicks and deops, and also from deprotects by any other users."
mode char a, prefix & - protected member "This channel mode marks a user as protected. This means they may not be kicked or deopped. Only a +q user or a U:Lined server may give or take away channel mode +a under normal circumstances, or kick a +a user."
"Note that channel modes +q and +a do not infer channel mode +o. Channel mode +o is seperate, therefore allowing you to protect a user who is voiced or halfopped if you wish."
You can extract all supported modes and their prefixes from the server's 005 numeric, it looks like this on Zandronum IRC:
PREFIX=(ohv)@%+
> Do any servers allow to prepend more than one mode prefix to user name (for example: "@%+Dusk")?
Not by default and not necessary, only when a client explicitly requests the server to send him NAMES in said format (called NAMESX support).
|
|
|
|
(0006796)
|
|
Zalewa
|
|
2013-07-25 18:55
|
|
Quote
"Note that channel modes +q and +a do not infer channel mode +o. Channel mode +o is seperate, therefore allowing you to protect a user who is voiced or halfopped if you wish."
So how do a protected op, or a protected halfop appear? Do the '@', '%' and '+' prefixes take precedence over '&' and overwrite it? |
|
|
|
(0006797)
|
|
Konar6
|
|
2013-07-25 19:26
|
|
No, the higher status takes precedence, the order is: qaohv
(yeah, it can get messy) |
|
|
|
(0006801)
|
|
Zalewa
|
|
2013-07-25 21:33
|
|
|
I've added both of these in this commit. I consider this issue resolved. |
|