🚀 go-pugleaf

In article <1991Jun12.001917.239@gacvx2.gac.edu> dan@gacvx2.gac.edu writes:
>Greetings,
>[Sarcasm deleted]
>I would think that it would be better for the authors of cnews and other news
>systems to spend the time preventing their software from sending out old news,
>by fixing the conditions that cause old news to be sent, rather than filtering
>it from the net at large. 

Funny. That's exactly what they are doing. And certain people are bitching
overloudly and overlong about exactly that. You can't win.

Honestly, I don't see why this topic stays alive. Everyone knows what everyone
else thinks. Bitching and moaning about it isn't going to change things. So
can we drop it already?

If you want to do something about it that's different. The only solution I
like (which I posted a few days ago) has recieved no reply. A few other
solutions were proposed, but none are practical (I think) because they require
Henry to waste a lot of time writing code that needn't be written. If my
solution won't work, or if someone has a better one, well, let's hear it.
But-
1) If it requires H.S. and G.C. to write a lot of code, save your breath.
   They've got better things to do.
2) If it requires many many sites on the net to implement it (or even many
   Cnews sites), save your breath. Without being integrated into Cnews, it
   won't ever make it into the majority of sites.


BTW, there is an extremely-low-sophistication method of dealing with all this
that won't chew up too much bandwidth. Have automated scripts which send bounce
messages to sites sending out bad headers... But run them only once a month.
If every admin who reads this group set up such a script (trivial to write),
it still wouldn't be a major strain on bandwidth. The filtering effect of Cnews
would preserve locality of error-reporting, so that most bad hosts would only
get messages from a few hosts.

Come to think of this, I think Henry mentioned that he did something like this
before he released the new Cnews. But I wouldn't swear to it.

---
Alexis Rosen
Owner/Sysadmin, PANIX Public Access Unix, NY
alexis@panix.com
{cmcl2,apple}!panix!alexis