0003088: Is RPL_WHOREPLY (Raw 352) not rfc-compliant ?

ID	Project	Category	View Status	Date Submitted	Last Update
0003088	unreal	ircd	public	2006-10-12 19:50	2007-04-19 02:53

Reporter	Fabien	Assigned To
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	3.2.5

Summary	0003088: Is RPL_WHOREPLY (Raw 352) not rfc-compliant ?
Description	on a who nickname server answers with a chan name but not the operator status on it exemple: If I am operator on #test and I do a who I receive: * #test fabien XXX-FA6803E4 irc.existence.local fabien H :0 test. Other ( but I think it is a "feature" and not a "minor" ) who with hosts jokers don't work too (as rfc example WHO *.fi)
Steps To Reproduce	try a who on a chan operator (oper on his "last" chan)
Additional Information	My problem is that eggdrop updates status on raw 352. So, when an eggdrop do a who command (tcl script for example) on unrealircd server, it updates the status with potentially bad informations.

3rd party modules

Date Modified	Username	Field	Change
2006-10-12 19:50	Fabien	New Issue
2006-10-13 12:06	aquanight	Note Added: 0012485
2007-04-19 02:53	~~stskeeps~~	Status	new => closed
2007-04-19 02:53	~~stskeeps~~	Resolution	open => no change required

aquanight 2006-10-13 12:06 reporter ~0012485	I'm thinking this might be intended. Doing /who nick simply shoves the first visible channel in that slot, and as such the channel status might not be quite as useful. Channel status is given when you do /who #channel though.