Path: utzoo!attcan!uunet!husc6!bbn!csd4.milw.wisc.edu!mailrus!cornell!batcomputer!sun.soe.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: news.admin Subject: .signature database? Message-ID: Date: 24 Dec 88 20:51:44 GMT Sender: news@sun.soe.clarkson.edu Reply-To: nelson@clutx.clarkson.edu Organization: Clarkson University, Postdam NY Lines: 17 Has anyone ever considered a database of .signatures? After all, isn't it foolish for eric@snark.uu.net, or jfh@rpp386.Dallas.TX.US or henry@utzoo.UUCP's signature to be duplicated and retransmitted countless times? Why not keep a database of .signatures, one per user ID (the user ID is the key, you see), a maximum of N characters (N is subject to discussion). Create a new control message, 'signature', that gets sent out whenever the date on .signature is a month in the past. On that database end, if the user hasn't posted in a month, expire their signature entry. Doesn't work for mailing lists gatewayed to newsgroups, but hey, life isn't perfect. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) To surrender is to remain in the hands of barbarians for the rest of my life. To fight is to leave my bones exposed in the desert waste.