Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 beta 3/9/83; site cwruecmp.UUCP Path: utzoo!linus!decvax!cwruecmp!rrrm From: rrrm@cwruecmp.UUCP (R Robertson + R McGuire) Newsgroups: net.jokes.d Subject: reposting jokes over and over and over and over and over ........ Message-ID: <1133@cwruecmp.UUCP> Date: Fri, 6-Apr-84 14:02:36 EST Article-I.D.: cwruecmp.1133 Posted: Fri Apr 6 14:02:36 1984 Date-Received: Sat, 7-Apr-84 12:01:45 EST Organization: CWRU Computer Engr. Cleveland, Ohio Lines: 38 I have come up with a solution to the net.jokes problem of twenty different people posting the same joke all in quick succession. If you hear a good joke and plan on posting it doo the following: a) If you hear a joke from a person that you think might read net.jokes ask him/her if the net.jokes is infact the original source. If it is, DON'T repost it no matter how funny it was. b) read net.jokes and look for your joke. If you see don't post it. c) pick a random number, a, between 3 and 14. Continue reading net.jokes for a days before posting your joke. If you see the joke in that time period, don't post it. /* This way a person can tell two of his friends the joke, both of whom might post it. One person will pick, say, 10 days while the other could pick 6. The latter would then post the joke, the former would then read it and NOT post it. */ /* Granted, both of those people might both pick the same random number but this ought to cut down on joke re-telling a considerable amount. */ This still won't prevent people from posting an endless stream of BUMPER SNICKERS, YALBJ's, FUNNY BUSINESS NAMES, etc. but it should prevent Patty O'Furniture's name from showing up more than once a year. If you think this is a reasonable and viable plan let's hear from you. The more visible support this gets the more likely it is that it will be effective. (Peer pressure at its finest.) Ryan McGuire (the rm of rrrm)