The problem with UsenetThere's recently been a little bit of fuss in the news about the New York Attorney General getting various ISPs to turn off the alt.* hierarchy on their Usenet servers, with a number of people are wondering how the ISPs were willing to cave in to this sort of pressure. My guess, based on what I remember from being fairly involved with a Usenet server up until a couple of years ago, is that ISPs were probably just as happy to have a good excuse to cut back on their news servers. From an ISP's perspective, Usenet has a number of problems:
(Also, allegedly the users that do use your Usenet server will complain vociferously if you don't do an excellent job of carrying a full feed.) Given all this, it's no surprise that ISPs have been getting out of the Usenet game for some time, bit by bit; many have quietly outsourced it to specialist providers like Supernews or simply stopped providing Usenet entirely. This latest development is merely more noisy than usual. Removing all of the alt hierarchy is a little bit of overkill, but it's probably not like the ISPs care very much and handling alt.* has its own set of headaches. Sidebar: why dropping alt.binaries.* is actually effectiveNormally 'censorship' of this nature is ineffective, as the targeted group just relocates to some other forum, in this case some other newsgroup, and resumes their old behavior. This doesn't work on Usenet because it is very easy to recognize and drop binary postings in non-binary newsgroups, and tools to do it have been commonly available for over ten years now. (One such tool is cleanfeed .) |
These are my WanderingThoughts GettingAround This is part of CSpace, and is written by ChrisSiebenmann. * * * Atom feeds are available; see the bottom of most pages. Categories: links, linux, programming, python, snark, solaris, spam, sysadmin, tech, unix, web |