usenet's newsreader call-blocker

the universal "ignore" filter automatically demotes/flags all articles 
in all newsgroups, allowing only those articles, contributors, servers,  
topics, etc., which have been previously whitelisted, i.e. "unignored",
"promoted", "watched", "highlighted", "kept", etc., primarily based on
text strings in overview headers, e.g. "message-id *@server001*, which 
are added/modified/deleted at the user's discretion . . . it's similar  
to whitelisting phone calls, so only preapproved caller id numbers may
ring through to your phone and ignored caller ids still appear without
ringing . . . usenet's call-blocking app is the global "ignore" filter  
  
the chronic usenet offenders, primary and secondary troll aliases, are 
killfiled, and the unfamiliar troll aliases, tertiary, ephemeral, will  
remain buried in collapsed threads pending routine purges (e.g. daily),   
so no matter how may umpteen times per day/per newsgroup(s) they morph 
their headers, they cannot circumvent usenet's newsreader call-blocker
  
the "ignore" filter is easily activated in any newsreader, e.g., using  
forte agent, to set filter expression "author: *", kill action "ignore   
thread", scope "global", priority "100" . . . then "unignore"(unblock)
articles selectively, while automatically ignoring usenet's minions of 
predators (trollfarm, usenet's commission-only telemarketing chatbots) 
  
most usenet newsgroups subscribers (mainly lurkers, some contributors)  
probably have a hundred or more "killfile" entries that greatly reduce
visible newsgroup activity, making it easier to further whitelist some 
articles, while blacklisting a few more of gazillions of troll aliases   
(some newsgroups may attract fewer trolls than others...caveat emptor), 
and filtering by newsgroup sections, hierarchies, e.g. [news.*], using  
asterisks to shorten entries without oversimplifying, e.g. from *abcd*,
and beware insidious troll farm tactics, e.g., replies to known trolls 
are almost always from other troll puppets but not always, and this is  
where whitelisting prevents inadvertent filters, "guilt by association"