Feature Requests item #1670204, was opened at 2007-02-27 13:05
Message generated for change (Comment added) made by lschiere
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: rsk254 (rsk254)
Assigned to: Nobody/Anonymous (nobody)
Summary: Enhancements to blocklist function and performance

Initial Comment:
These aren't in any particular order -- but they're somewhat
related to each other.

1. Separate block list storage from buddy list storage -- that is,
use a different config file, perhaps "block.xml"?

Reason: will make it easier (perhaps) to do some of the other
things I'm about to suggest.  May allow use of different (perhaps
optimized) algorithms -- at least in my case, the buddy list
is "a few dozen" while the block list is "several thousand".
May facilitate future sharing of block lists without inadvertent
sharing of buddy lists.

2. Support block lists that are per-handle and per-chat-protocol.
(I was going to suggest "global", that is, across all chat
protocols, but I don't see need for it, at least not yet.)

Thus, blocking could be:

        - per-handle ("block fred when I'm logged on as barney")
        - global per protocol ("block fred")

Reason: if I've identified a bot, then I don't want to hear from
it when logged in with any handle.

3.  The current block list implementation seems to incur a large
startup delay when the list of handles exceeds a few hundred.
Is there something that runs worse than O(n) reading that list?  
(I'm looking through the code now but strongly suspect that 
someone more familiar with it is very likely to find this well
before I do.)

4. Ability to use regexp's for blocking.  Reason: there
are a lot of bots whose names follow patterns, e.g.


Comment By: Luke Schierer (lschiere)
Date: 2007-04-12 12:16

Logged In: YES 
Originator: NO

As we are closing this tracker, please submit any feature request that is
still valid to http://developer.pidgin.im.  Thanks. 


You can respond by visiting: 

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
Gaim-features mailing list

Reply via email to