ra@rlgvax.UUCP (07/02/83)
# of Avg #
Articles Lines
75 12 rh@mit-eddi.UUCP
31 29 laura@utcsstat.UUCP
28 17 cfv@packet.UUCP
27 4 alb@alice.UUCP
24 36 tim@unc.UUCP
21 10 grw@fortune.UUCP
21 2 rst@houxu.UUCP
18 44 smk@linus.UUCP
16 30 spaf@gatech.UUCP
16 21 mat@hou5e.UUCP
16 20 berry@fortune.UUCP
16 15 leichter@yale-com.UUCP
15 19 larry@grkermit.UUCP
14 412 map@cbosgd.UUCP
14 14 trb@floyd.UUCP
14 14 madrid@auvax.UUCP
13 10 jim@uw-beaver.UUCP
13 7 dave@utcsrgv.UUCP
12 25 mark@cbosgd.UUCP
12 22 knudsen@ihnss.UUCP
12 17 silver@csu-cs.UUCP
12 10 furuta@uw-beaver.UUCP
11 16 peterr@utcsrgv.UUCP
11 14 rfw@aplvax.UUCP
10 39 ucbesvax.turner@ucbcad.UUCP
10 16 wex@ittvax.UUCP
10 12 ron@brl-bmd.ARPA
10 7 presley@mhuxj.UUCP
9 50 trc@houti.UUCP
9 35 ddw@cornell.UUCP
9 21 bill@utastro.UUCP
9 21 chris@umcp-cs.UUCP
9 18 bstempleton@watmath.UUCP
9 16 raf@loux.UUCP
9 15 msc@qubix.UUCP
9 14 tower@inmet.UUCP
9 14 oz@rlgvax.UUCP
9 12 norskog@fortune.UUCP
9 10 govern@houxf.UUCP
9 7 pdl@root44.UUCP
8 34 mjk@tty3b.UUCP
8 23 karn@eagle.UUCP
8 22 fostel@ncsu.UUCP
8 21 guy@rlgvax.UUCP
8 19 tom@rlgvax.UUCP
8 10 goldfarb@ucf-cs.UUCP
7 75 parnass@ihuxf.UUCP
7 32 jim@mcvax.UUCP
7 31 ras@philabs.UUCP
7 31 barto@bmcg.UUCP
7 25 ucbmonet.arnold@ucbcad.UUCP
7 25 rael@inuxe.UUCP
7 22 smh@mit-eddi.UUCP
7 18 jdd@allegra.UUCP
7 17 edhall@rand-unix.ARPA
7 16 hal@cornell.UUCP
7 15 mark@umcp-cs.UUCP
7 13 ken@turtleva.UUCP
7 12 lab@qubix.UUCP
7 12 rconn@brl.ARPA
7 12 gwyn@brl-vld.ARPA
7 11 rwhw@hound.UUCP
7 11 grunwald@uiucdcs.UUCP
7 10 woods@hao.UUCP
7 9 futrelle@uiucdcs.UUCPsmk@linus.UUCP (Steven M. Kramer) (07/03/83)
I'm hnored to be one of the top users on the net.
Whoops, is this another article? (Sorry, I'm not in the habit of doing
this, but I couldn't resist. If I also posted this to net.jokes,
their followups would mess up the articles here.)
--
--steve kramer
{allegra,genrad,ihnp4,utzoo,philabs,uw-beaver}!linus!smk (UUCP)
linus!smk@mitre-bedford (ARPA)bstempleton@watmath.UUCP (Brad Templeton) (07/03/83)
Well, thanks for submitting this info. It shows something which will become even more and more of a problem when the net grows. Here we have a new site (mit-eddi) which was by an order of magnitude the biggest poster on the net, and which contained the user who posted the most as well, again by a substantial margin. If everybody had as much to say as these guys, the net would very quickly collapse of its own weight. We need something more to help educate new users as to the size of the net and the net etiquette rules that have developed. This means that news software has got to insist that people know this, and be quite verbose in warnings etc. on posting. (This is justified, since one posting can equal at least several thousand readings) The problem is that there are always old sites out there running old stuff and we can't effect such changes. Thus I suggest we adopt in the news software a system to help encourage people to update. This would consist of code that checks the system clock against the expiry date. If the code has expired, it either fails to work or prints out "This code has expired. Please install an update etc..." every time it is used. Now we can't hide this code, so a nasty system administrator could delete it, but this itself would be a reminder that the code is out of date. We could go even further. What we have is essentially an anarchy on the net, and the only way to get things done is by technocratic methods. We could actually go so far as to have news systems send special header items similar to passwords, encripted with the posting date so the password can't be figured out. Once a password expires, it and the new password would be accepted for a given number of weeks (perhaps 4) and after that no incoming articles with a bad password would be accepted. Thus any site that doesn't update will still pass on news but will not get any of their generated news accepted on the net. This does sound rather harsh, and it's certainly quite far from the track of any software policy I have heard of, but I would like to get comments on this philosophy. I realize many sites don't have the time to keep track of updates. This scheme means that sites that have the time to post news must also have the time to post it correctly. None of this apples to readnews, though. Mostly it applies to inews because it by posting only that we are members of a community which will soon need laws. -- Brad Templeton - Waterloo, Ont. (519) 886-7304
leichter@yale-com.UUCP (Jerry Leichter) (07/03/83)
Oh, the pain of it all! Here I make it into the "top 10" of article submitters just before leaving the net (for 2 months or so, anyway). (Do I hear sighs of relief out there?) The most frustrating thing is that I'll be able to continue READING the news (through a recently added feed into DEC) but unable to respond (except maybe very rarely.) So if ANYONE out there says ANYTHING disagreeing with me in the next two months - you are being very unsporting and kicking a man when he is down! (In weakness, strength.) Anyway, thanks to rlgvax!ra for the statistics. A note to anyone considering collecting such: I'd be curious for a distribution of submitters vs. newsgroups (both how many and what clusters of newsgroups given people submit to, and the number of different people submitting articles to a given newsgroup (and the percentage in each group submitted by, say, the top 5 submitters).) -- Jerry decvax!yale-comix!leichter leichter@yale [If you write to either I will answer after a while...]
cfv@packet.UUCP (07/04/83)
This doesn't sound technocratic, it sounds like a wonderful dictatorship. Has
anyone really defined what is WRONG with the current system? My feeling is
that while there are problems, the net works. I don't like fixing things
that aren't broken.
--
>From the dungeons of the Warlock:
Chuck Von Rospach
ucbvax!amd70!packet!cfv
(chuqui@mit-mc) <- obsolete!