Re: alt.hackers unmoderated?
Article: 8917 of alt.hackers From: firstname.lastname@example.org (Jeff Mercer) Newsgroups: alt.hackers Subject: Re: alt.hackers unmoderated? Date: 22 Oct 1995 08:43:03 GMT Organization: Green Hell, Inc. Lines: 49 Approved: email@example.com Message-ID: firstname.lastname@example.org Reply-To: email@example.com NNTP-Posting-Host: freenet4.afn.org X-Newsreader: NewsWerthy 1.82 Status: RO
firstname.lastname@example.org (Jan Kasprzak) wrote: JK> My news system writes to me: JK>: Date: Mon, 16 Oct 1995 13:08:13 +0100 JK>: JK>: newsgroup alt.hackers was changed to unmoderated by email@example.com JK> Is this correct?!? Well it probably is for that server... Individual news servers can be tailored any number of ways, and if the admin for that server decided to make the group unomoderated on that site, he can. This of course means that anyone who uses that server can now post here without even performing one of the most trivial hacks there is... What a fuckin' sham. I guess the asshole sysadmin decided we were "oppressing freedom" or some other bullshit. It certainly does explain the garbage that's been popping up here. I'm rather pissed off about this, actually. If it continues, I'll be dropping out of this group, possibly out of Usenet all together... Maybe we can make a moderated mailing list or something but damn it, I can't handle any more mail... ObI'mPissedHack: The UF VAX system tended to have a very strict quota level (300 blocks for personal accounts, which is only 150K of space). One way to get around this problem was to temporarily exceed your quota, but there's a lot of things you can't do with exceeded quota. On a VAX/VMS system, you can send a file to yourself with the SEND/FILE command. The file is sent via a BitNettish protocol and is stored on a different disk in a special receiving area. There's no limit on how many files you can have waiting to be received, or how big the files can be (except of course for how much space is free on that disk). However, after a file has been waiting for several days, it's purged automatically. So I wrote a simle DCL program and submitted it as a Batch job. It'd send all the files in a subdirectory to my account, then delete the files and re-submit itself so that it'd run again in several days. When it wakes up it'd go into exceed quota mode (a previously posted hack), receive all the files into a sub-directory, then repeat the earlier process. Worked great. firstname.lastname@example.org : "Humph! Bugger off!" Jeff The Riffer : --Dwarven Proverb. Drifter... : Homo Postmortemus :