Opened 9 years ago

Last modified 9 years ago

#10690 new enhancement

Protected ops don't show on IRC user list

Reported by: ognobogvoshno Owned by: elb
Milestone: Component: IRC
Version: 2.6.3 Keywords: irc ops userlist user list
Cc:

Description

As I understand it, pidgin's assigning of icons in the user list on IRC is based on /names. (i.e. +johnsmith gets the voice icon). & is ignored in that list - I suggest making a new icon for protected ops so &johnsmith doesn't just show up in regular users

Change History (3)

comment:1 Changed 9 years ago by rekkanoryo

  • Type changed from patch to enhancement

There is no patch or actual code change on this ticket. It should not be set to patch.

That said, I don't recall & being a standard mode character, thus our supporting it would be contingent upon whether or not the various IRC daemons treat that the same way when used as a mode character. If it means "protected ops" on daemon X and something else on daemon Y, then we'll continue to just ignore it.

comment:2 Changed 9 years ago by elb

Not only is it not standard, it's almost completely broken -- & is a valid channel specifier in the original standard.

If the server in question sends an 005 with PREFIX=, we should at least be stripping it off, I believe. If it does, and we're not, that's a bug.

comment:3 Changed 9 years ago by zackf

Servers such as Rizon's have been using the ampersand to denote +ao (protected OPs) in a channel for some time now. Since most IRCds would not allow the use of an ampersand in a nick, I'm afraid I do not understand why this has not yet been applied.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!