Multiple Modes Glitch - 05/10/05 09:39 AM
I've been testing several IRC clients and servers on this and I am getting this glitch everywhere I go. I have also asked this question to the Unreal IRC development team but I wander why this bug / glitch appears and how it should be handled (on the server or on the client-side).
It works as follows:
- User1 joins an irc server and makes a channel.
- User1 now has operator status on this channel.
- User1 does a MODE +v on the channel and himself. This will make him have a second-status as voice.
- User2 now joins the channel made by User1.
- User1 deops himself (he will have voice-status on the server).
- User1 now sees the + sign (for voice) in front of his nickname in the nicknames-list.
- User2 does not see this prefix in front of the nickname of User1.
When User2 does a WHOIS on User1 mIRC will see that this user has voice-status on the channel but will not correct the prefix in the nicklisting.
When User2 does a NAMES on the channel mIRC will silently fix it and add the + prefix in the nicklisting.
Is this an actual bug? And evenmore...is this a bug on the client or on the server-side? I've been checking both the IRC Protocol (rfc1459) and the IRC: Client Protocol (rfc2812) for an answer but none specify how multiple modes should be handled.
Anyone with an answer?
It works as follows:
- User1 joins an irc server and makes a channel.
- User1 now has operator status on this channel.
- User1 does a MODE +v on the channel and himself. This will make him have a second-status as voice.
- User2 now joins the channel made by User1.
- User1 deops himself (he will have voice-status on the server).
- User1 now sees the + sign (for voice) in front of his nickname in the nicknames-list.
- User2 does not see this prefix in front of the nickname of User1.
When User2 does a WHOIS on User1 mIRC will see that this user has voice-status on the channel but will not correct the prefix in the nicklisting.
When User2 does a NAMES on the channel mIRC will silently fix it and add the + prefix in the nicklisting.
Is this an actual bug? And evenmore...is this a bug on the client or on the server-side? I've been checking both the IRC Protocol (rfc1459) and the IRC: Client Protocol (rfc2812) for an answer but none specify how multiple modes should be handled.
Anyone with an answer?