[Konversation-devel] [Bug 305166] New: Options for ident, nick and host for bans / quiets / similar things

[Fuchs]

https://bugs.kde.org/show_bug.cgi?id=305166

            Bug ID: 305166
          Severity: wishlist
           Version: Git
          Priority: NOR
          Assignee: konversation-devel at kde.org
           Summary: Options for ident, nick and host for bans / quiets /
                    similar things
    Classification: Unclassified
                OS: Linux
          Reporter: develop at fuchsnet.ch
          Hardware: Other
            Status: UNCONFIRMED
         Component: general
           Product: konversation

For quiets and bans it would be very handy to have short options for nick,
ident, host  (and maybe others like account if the network supports it) which
are combinable. 

e.g.  /ban -ih testuser    would set a ban matching the current ident _and_
host of testuser,  /quiet -nh testuser would set a quiet matching the current
nick and host.  The missing parts would be filled up with wildcards (*).  A
usability problem I see is that /ban testuser would do a *!*@* then, which is
silly. So either 1) it has to be inverted, e.g. use wildcards for the given
options or  2) use a separate command for it  (imo not good) or 3) treat the
default with no options at all different (not really consistent) 

The current implemetnation with [-host|-domain| -userhost|-userdomain] is not
that flexible plus the host/domain thing works a bit strange with cloaks from
what I got. So having a possiblity to just specific parts of the 
nick!ident at host  and combine them would, if I don't miss anything, offer all
the flexibility advanced users (operators) need.  

Reproducible: Always

Steps to Reproduce:
1. Need to set a specific ban / quiet in a quick way

Actual Results:  
Find no possibility to do so

Expected Results:  
Have a flexible way to ban / quiet users, without having to specify the mask
manually (which is time consuming) or via copy & paste (which can be hard in an
active channel)

-- 
You are receiving this mail because:
You are the assignee for the bug.