news.sackheads.org logs

List of groups

sackheads.general General waffling
sackheads.config Discussion of sackheads hierarchy
sackheads.freakshow You have to ask?
sackheads.bozo.flatty You have to ask (part 2)?
sackheads.test Where all the warez gets traded
sackheads.uffh Unix Freaks From Hell
sackheads.uffh.haybaler Our fav. penis extension - haybaler

Rules of Carriage

These rules are borrowed from Usenet II, with thanks. (All our machines are Usenet II sound, are yours?)
We've made some minor changes where applicable.

Header compliance: "Sound Messages in a Healthy Net"

sackNet messages are well-formed. Unsound messages may be dropped or canceled locally by any sackNet site and cancelled within sackNet by the SackHeads news cabal, or in the future, we may make use of an automated janitor.

This document is to be considered an addendum to RFC1036 and supplements, and the basic specifications for a well-formed message can be found there.

An article must be self-consistent. If the subject line starts with "Re:", it is a followup, and there must be a references line to prevent orphan threads. The converse, however, is not true: a followup does not need to start with "Re:"... it is always legitimate to add a new topic to a thread.

All articles posted to sackNet must have the distribution "darkart". sackNet sites are expected to put this into their "distrib.pats" files (or equivalent), so users don't need to do this manually. This serves as an additional filter against sites outside the net tunneling unsound messages in.

Crossposts between sackheads.* and any other hierarchy are unsound. Crossposted messages will be canceled by the automated janitor, the sackNet news cabal, or just dropped on the floor.

Crossposting: "The Rule of Three"

No article in the world is relevant to more than a small handful of groups. If WWIII is announced, it will be announced in a group such as net.headlines.world-war-three

No article shall be crossposted such that it will spawn a thread in more than three groups. If it is necessary to post to more than three (for example, an announcement of a vote in a subhierarchy that uses voting for group creation) followups shall be set to a subset of three or fewer of the original groups. Where possible, this will be enforced by the janitor, or the sackNet news cabal.

Posting the same article multiple times to get around the rule of three is extremely unsound behavior. It is acceptable to post the same article up to three times, to avoid the generation of a permanent floating flame war between groups that are known to be antagonistic towards each other, or to comply with a group's policy against crossposting.

Posting the same article every day or every week to get around the rule of three is unsound behavior. If an article is expected to hang around for a month it should have an expiry date set a month in the future. If your newsreader doesn't support adding an Expires header, then see the recommendations for Usenet II software.

It is never permissible to post a message more than three times or to more than ten groups in total, no matter how many times it's posted or how the followups are set.

Cancellation of messages

ONLY the following entities are authorized to cancel messages:

the original poster
the administrator of the originating sackNet site
the moderator of (any) group in which it was posted
the sackNet news cabal, or a future automated janitor acting for the cabal.
"spam-cancellers", ie those following the Spam Cancel Guidelines

A forged cancel can be defined as one which doesn't meet the above criteria, and would be declared rogue by Andrew Gierth's Cancel Analysis (see news.admin.net-abuse.bulletins)

A forged cancellation from any party is considered *highly* unsound behavior, and sackNet admins should take any steps necessary to ensure that their site is not used for this purpose.

Carrying sackheads.*

Getting a feed

sackheads.* should appear in your existing feed, if not, we may be able to help... pls email news@sackheads.org

Configuring your news server

INN control.ctl entries

PGPverify

###
### sackNet - see http://www.sackheads.org/news/
###
checkgroups:news@sackheads.org:sackheads.*:verify-sackheads.config=checkgroups
newgroup:news@sackheads.org:sackheads.*:verify-sackheads.config=newgroup
rmgroup:news@sackheads.org:sackheads.*:verify-sackheads.config=rmgroup

Without PGPverify

###
### sackNet - see http://www.sackheads.org/news/
###
checkgroups:news@sackheads.org:sackheads.*:mail
newgroup:news@sackheads.org:sackheads.*:doit=newgroup
rmgroup:news@sackheads.org:sackheads.*:mail

PGP key

Type Bits/KeyID    Date       User ID
pub  1024/F2596D65 1998/03/16 sackheads.config

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3i

mQCNAzUNSjEAAAEEALQjcwIegnaZKgMj/9313XKWgxBAjTz23yqrs/JuIKMsU5vh
UP55xX5KHIqt6KBKn7SXVtnjvTuRwl7GQbfutg5dIXtwc/Eole6QSrdROo4agi4b
sdqjTRetBRii/doZj16p/3TL7R49sCEkXz9Ck4KYzzNOCUpu+R+74vryWW1lAAUR
tBBzYWNraGVhZHMuY29uZmlniQCVAwUQNQ1fPAhVPWGcTAd1AQGnbAP/fY6qegDn
0pYwM2/aLzmce3Do/DxFh+UsLXrY11g02A823xHfDYMfWqF3DFIWA7IHOLrlswOr
tQfjmVfnI9hbo2aPmw96UYqsUiDkucIONJihPqWizmZD5qTh0imfEtSTihj90ovo
QmjnucEOpyHI3Jud7jH6Gj2w6VTrasvM8jyJAJUDBRA1DUpv9nfmhR6rRJEBAUTf
BACxxheDtHaPufmeblWO/EOgXoQP7lWygg33QAjy5mP011b5YmggQtdVvVmEfAtD
XM2bk9PMisOKgAlvvS7gbEk0jDbCULpU3tEEweZ0yPlp7kT8VFoGtEjhTxy+qUOf
Hil8BA3cWZlGlB6reKkbHc423KfOvkK4dpiH/uotkQtSeIkAlQMFEDUNSjIfu+L6
8lltZQEBhewD/ioWaqkWDRxGI2Yiwbs4p7WB2XajuGk5ZcLPsRK6VF6jwKoWga1s
/ozLfvdPankeT+x8LcOmdx8Xz+sO2HQSQufVT2SA0y2fQnpGxZpGDu4IVpkKJBTB
gd2QDKYcoRNy87arHTtA1iM8O9dgG+w3pq9ELFRfEonAlWgJNywAHN0q
=ckF8
-----END PGP PUBLIC KEY BLOCK-----