Bug #1378
Quassel should not show wallops as operwalls
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/19/2015
Due date:
% Done:
0%
Estimated time:
Version:
0.10.0
OS:
Any
Description
Steps:
1) Send a wallop.
Expected result:
20:50:09 WALLOP mist: Wallop!
Actual result:
[20:50:09] * [Operwall] mist: Wallop!
Context:
Wallops and operwalls are different things.
OPERWALL :<message> Sends an OPERWALL message of <message> to all opers who are umode +z - Requires Oper Priv: oper:operwall
WALLOPS :<message> Sends a WALLOPS message of <message> to all users who are umode +w (including non-opers). Server sent WALLOPS go to all opers who are umode +w. - Requires Oper Priv: oper:mass_notice
History
#1 Updated by gry over 8 years ago
void EventStringifier::processIrcEventWallops(IrcEvent *e)
{
displayMsg(e, Message::Server, tr("[Operwall] %1: %2").arg(e->nick(), e->params().join(" ")));
}
I don't really understand where Quassel processes the "real" operwalls now...