Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.mobile.android > #154307 > unrolled thread

blacklist filters

Started byD <J@M>
First post2026-06-29 15:24 +0200
Last post2026-06-29 17:01 +0200
Articles 2 — 2 participants

Back to article view | Back to comp.mobile.android


Contents

  blacklist filters D <J@M> - 2026-06-29 15:24 +0200
    Re: blacklist filters Jörg Lorenz <hugybear@gmx.net> - 2026-06-29 17:01 +0200

#154307 — blacklist filters

FromD <J@M>
Date2026-06-29 15:24 +0200
Subjectblacklist filters
Message-ID<5af11c7ef715b14abb06f2d35bdfbbba@msgid.frell.theremailer.net>
blacklist filters on overview headers are used to automatically move/delete 
common troll aliases, using wildcards */" to minimize the length of entries
without oversimplifying, which, depending on newsgroup activity, can expand  
into hundreds of unique text strings per line, e.g., using 40tude dialog to
automatically move all troll posts to the "troll" folder, !move(troll) from   
"troll001" "troll002" "troll...", i confine line length to ~1024 characters  
for ease of editing (afaik 4095 is recommended maximum), which allows about
120 unique entries per line, and the "!move" action can be applied to other 
overview headers, e.g. "!move(troll) subject" and "!move(troll) message-id", 
but the total number of unique filter entries and actions should be kept to
a minimum (e.g. i keep no more than <500 blacklisted, and <100 whitelisted),  
allowing the global ignore filter to move the more ephemeral aliases always 
to the "junk" folder which may then be browsed before purges, if needed, as   
new whitelistings might exist, but ignored headers are almost always trolls,   
encouraging users to whitelist helpful contributors, and purge the unknowns
  
so it's important to avoid killfiling unfamiliar aliases unless they become 
chronic, which, if you're doing it correctly, should eliminate about 99% of
new/unread articles from your newsreader's viewing window, and leaving only 
whitelisted/watched (the ignored/moved article headers you can also filter),  
using whitelist or watch filters on overview headers to automatically watch
real (non-chatbot) contributors, while the global ignore filter !move(junk) 
from * automatically moves everything else (troll farm chatter) to the junk   
folder, thus only articles posted from watched contributors/topics/servers/
etc. bypass the global ignore flag, even those that are cross-posted, which  
greatly reduces visible newsgroup article headers in some newsgroups, while 
rendering other newsgroups deaf as a post... this keeps the troll farm away, 
having already killfiled hundreds of the most common troll aliases/subjects,
allowing cursory review of the junk folder before purging, sometimes to add  
another killfile entry, or more rarely a new whitelisting . . . the "troll"  
folder exists to test new blacklist entries, then troll and junk are purged
   

[toc] | [next] | [standalone]


#154308

FromJörg Lorenz <hugybear@gmx.net>
Date2026-06-29 17:01 +0200
Message-ID<111u1cf$1nso3$1@solani.org>
In reply to#154307
On 29.06.26 15:24, D wrote:
> blacklist filters on overview headers are used to automatically move/delete 
> common troll aliases, using wildcards */" to minimize the length of entries
> without oversimplifying, which, depending on newsgroup activity, can expand  
> into hundreds of unique text strings per line, e.g., using 40tude dialog to
> automatically move all troll posts to the "troll" folder, !move(troll) from   
> "troll001" "troll002" "troll...", i confine line length to ~1024 characters  
> for ease of editing (afaik 4095 is recommended maximum), which allows about
> 120 unique entries per line, and the "!move" action can be applied to other 
> overview headers, e.g. "!move(troll) subject" and "!move(troll) message-id", 
> but the total number of unique filter entries and actions should be kept to
> a minimum (e.g. i keep no more than <500 blacklisted, and <100 whitelisted),  
> allowing the global ignore filter to move the more ephemeral aliases always 
> to the "junk" folder which may then be browsed before purges, if needed, as   
> new whitelistings might exist, but ignored headers are almost always trolls,   
> encouraging users to whitelist helpful contributors, and purge the unknowns
>   
> so it's important to avoid killfiling unfamiliar aliases unless they become 
> chronic, which, if you're doing it correctly, should eliminate about 99% of
> new/unread articles from your newsreader's viewing window, and leaving only 
> whitelisted/watched (the ignored/moved article headers you can also filter),  
> using whitelist or watch filters on overview headers to automatically watch
> real (non-chatbot) contributors, while the global ignore filter !move(junk) 
> from * automatically moves everything else (troll farm chatter) to the junk   
> folder, thus only articles posted from watched contributors/topics/servers/
> etc. bypass the global ignore flag, even those that are cross-posted, which  
> greatly reduces visible newsgroup article headers in some newsgroups, while 
> rendering other newsgroups deaf as a post... this keeps the troll farm away, 
> having already killfiled hundreds of the most common troll aliases/subjects,
> allowing cursory review of the junk folder before purging, sometimes to add  
> another killfile entry, or more rarely a new whitelisting . . . the "troll"  
> folder exists to test new blacklist entries, then troll and junk are purged

Troll!

[toc] | [prev] | [standalone]


Back to top | Article view | comp.mobile.android


csiph-web