0001427: Half-op prefix is not recognized in queries (PM) in IRC

Notes
(0006784) Konar6 (reporter) 2013-07-24 08:23	The problem with Doomsseker IRC is more serious regarding halfops - it doesn't support halfops at all.

(0006790) Zalewa (developer) 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 (reporter) 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 (developer) 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 (reporter) 2013-07-25 19:26	No, the higher status takes precedence, the order is: qaohv (yeah, it can get messy)

(0006801) Zalewa (developer) 2013-07-25 21:33	I've added both of these in this commit. I consider this issue resolved.

This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2013-07-24 01:07	Alien	New Issue
2013-07-24 08:23	Konar6	Note Added: 0006784
2013-07-25 17:26	Zalewa	Assigned To	=> Zalewa
2013-07-25 17:26	Zalewa	Status	new => assigned
2013-07-25 17:52	Zalewa	Note Added: 0006790
2013-07-25 17:52	Zalewa	Status	assigned => feedback
2013-07-25 18:50	Konar6	Note Added: 0006794
2013-07-25 18:54	Konar6	Note Edited: 0006794	View Revisions
2013-07-25 18:55	Zalewa	Note Added: 0006796
2013-07-25 19:26	Konar6	Note Added: 0006797
2013-07-25 21:33	Zalewa	Note Added: 0006801
2013-07-25 21:33	Zalewa	Status	feedback => resolved
2013-07-25 21:33	Zalewa	Fixed in Version	=> 0.11 Beta
2013-07-25 21:33	Zalewa	Resolution	open => fixed
2018-09-29 14:47	WubTheCaptain	Status	resolved => closed

Relationships