|
Grex > Agora35 > #21: An item in which Grex's staff crosses the line ... | |
|
| Author |
Message |
| 25 new of 163 responses total. |
mdw
|
|
response 40 of 163:
|
Sep 25 05:57 UTC 2000 |
I don't see any benefit to putting a long list of do's, don'ts, or
consequences into newuser. It's most all common sense, and in fact most
people can figure it out. Even for the few that might benefit, putting
it in newuser is moderately pointless. It certainly would not have
helped in the least with this particular case. There's no question but
that this person had much experience with this kind of environment, so
to the extent he was constitutionally capable, he would already have
understood what was not acceptable behavior, and what the likely
consequences were. From the arguments presented by this person, it
seems extremely likely he was "testing the limits". A more explicit set
of rules is not likely to have helped at all in this situation, because
it would have only solidified the notion in his head that he could rely
on external governance of his behavior, and externalize any blame for
the consequences of his behavior. This is of course a very popular
solution in small to medium sized social groups where the power figures
have more actual power and greater discretionary ability to administer
corporal punishment as needed to the posterior of any offenders. It's
not such a useful solution on grex, where there are significant
statuatory limitations on the power and authority of "those in charge",
and in many cases, a numbers and distance problem as well.
|
scott
|
|
response 41 of 163:
|
Sep 25 11:27 UTC 2000 |
Actually, there is no "problem user" list as such. If somebody is noticed
running bad programs, then a staff member (whoever's on Grex, basically) will
try to figure out the extent of the problem. ie., is the home directory full
of vandal tools, or is the user just a newbie program who accidentally created
an infinite loop?
It's usually quite easy to tell the difference, and with vandals it's usually
some form of immediate action (typically locking the account).
Borderline annoyances (repeatedly running idle-zapper escapes and such) get
some notice (I usually just disable their toys in a way that will announce
itself, since vandals often don't bother reading their email), and on repeated
occurrences get their account locked or something. So there is a very
short-term memory of individuals, but nothing like a list.
|
md
|
|
response 42 of 163:
|
Sep 25 11:57 UTC 2000 |
You people are being awfully inconsiderate of willard. Try and have a
little empathy. Imagine you are in willard's place, and ask yourself
how he must feel suddenly learning that he is regarded merely as the
latest in a long series of anonymous vandals/twits. Nothing special.
A familiar and commonplace annoyance. A small face in a big crowd,
treated no differently than any of the others. Add any minor self-
esteem issues willard might have, and the unpleasantness of your
treatment of him begins to seem cruelly deliberate. Shame on you.
|
ashke
|
|
response 43 of 163:
|
Sep 25 15:29 UTC 2000 |
This would be a suprise, md?
Willard, grow up. You knew when you did it that the masstels and the
idlezapper would get you in trouble. The ability of the staff to get rid of
those has nothing to do with the childish, annoying, attention hungry antics
you like pulling. If you were using a computer where I work, they have an
imaging program, and things with certian extensions get deleted, no question,
just happens when you reboot the computer.
Get over it, you did something you knew was bad, you got your hand slapped.
If you aren't prepared for someone to go into it, don't put it on here.
Simple. You don't own it, it's a free system based on some kind of honor
code, so don't be an ass. Well, anymore than you have already been.
|
willard
|
|
response 44 of 163:
|
Sep 25 16:12 UTC 2000 |
I'm sorry, I thought Grex was different than the computer where you
work. My mistake. I apologize. :-P
|
ashke
|
|
response 45 of 163:
|
Sep 25 17:03 UTC 2000 |
No, you're PC is different from the computer where you work. Grex you don't
own, so you don't get to flit about doing whatever you want. We all have a
responsibility to it's wellbeing, and to act in a way that is decent to others
and the rules.
|
janc
|
|
response 46 of 163:
|
Sep 25 17:05 UTC 2000 |
To be technically precise, the document quoted above is not Grex's privacy
policy. A policy would have have to be enacted by the board or by the
membership. The document quoted above is an ad hoc description by staff of
their normal policies and procedures. It's written half for internal use,
to try to give staff members a sense of what other staff members think is
sensible, and half to inform users of what our thinking on things is.
In saying that, I don't mean to suggest that we don't want to live up to
what is there. I do mean to suggest that lawyerly nitpicks over the exact
wording of the document won't necessarily get you anywhere. If you say
"what staff did doesn't exactly fit what the document says" then we have
two possible responses: change our behavior or change the document. This
will remain true until an actual policy is passed. Actually writing a
document that does say precisely the right thing would be so hard that I
suspect it will never happen. The staff notes on privacy serves a useful
function in the abscense of a formal policy.
To address the particular points:
- If staff found willard's postings in Agora so annoying that they decided
to go fishing through his directory looking for nasty stuff, then that
would be extremely inappropriate behavior. I don't believe that
happened here.
- If staff had some good reason to suspect that willard was running an
idle blocker, then doing a limited search through his directories to
confirm this is justified. I think this is what happened. Note that
the one he called 'watch' wasn't noticed for a while. Nobody did a
search through all his files for idle blockers. Only when we had
clues that 'watch' needed looking at did we look at it.
- Use of an idle-blocker wastes system resources and reduces Grex's
availability. If lots of users did it, getting access to Grex would
be extremely hard. This is a clear impact on Grex's "performance."
Willard's reading of this suggests that "performance" is only CPU
speed. It isn't. Possibly better wording is needed here, but I think
it should be obvious that hte "performance" we are interested in is
everything that effects the ability of Grex's system to provide
services to users.
- The telnet-bomb thing is more ambiguous than the idle blocker. The
privacy notes do not include a list of all the things that constitute
"abuse." It is a privacy statement, not a "conditions of use"
statement. The paragraph about mere rudeness not being "abuse" doesn't
mean what willard wants it to though. It means that mere content of
messages is not a reason to treat a user as a villian. So sending
rude tels does not justify searching a users directory, and tel-bombing
is against the rules even if you use it only to send polite messages.
This could use some clarification.
- There is no 'list' of bad-guys people get on. If you run a fork bomb,
we take immediate action. Staffers have memories though. A person who
has caused problems in the past is likely to be suspected more easily
in the future. After willard was found running an idle blocker the first
time, staffers probably were paying a little more attention to his
login times and process lists than they were with other users. But
basically when an incident is over, it's over.
- In the best of all possible worlds we would spend more time talking to
people about what they did wrong. We used to do so. But it takes a lot
more time. Write a message to the user, explaining the error of his
ways. If he replies, maybe engage in a conversation. If not, remember
to come back and check if the user stopped or not. Staff rarely has time
for this these days, not with a couple of these every day. We tend to
try to handle things in one transaction and forget about it.
|
rcurl
|
|
response 47 of 163:
|
Sep 25 17:07 UTC 2000 |
Re #40-41: there is a slightly higher standard of having procedures for
these situations because Grex is a 501(c)3 tax exempt charitable
corporation, with responsibilities to the public. Dealing with the
destructive behavior of users can't be entirely by personal fiat of staff
- there should be *some* rules.
|
willard
|
|
response 48 of 163:
|
Sep 25 18:40 UTC 2000 |
You people make me sick.
|
rcurl
|
|
response 49 of 163:
|
Sep 25 18:57 UTC 2000 |
We'll send (virtual) flowers.
|
twinkie
|
|
response 50 of 163:
|
Sep 25 19:00 UTC 2000 |
From popcorn@tir.com Mon Sep 25 14:59:58 2000
Date: Thu, 30 Mar 2000 00:05:58 -0500
From: Valerie Mates <popcorn@tir.com>
To: Kevin Nicholls <twinkie@cyberspace.org>
Cc: staff@cyberspace.org
Subject: Re: mass tels
Hm. That's a good question. I don't think anything like an AUP is all
collected together in one place on Grex. There's a bit of a discussion of
acceptable uses of Grex in the newuser program. There are bits and pieces
in the FAQ. And there are bits of information elsewhere too. I know for
years the staff has been telling users that sending mass tels is not an
acceptable use of Grex, but I don't think this is formally posted anywhere.
I'm torn between saying, "we could do better at posting this; we should
write something up" and "One of the founding philosophies of Grex was to
have as few rules as possible, since as soon as you make rules people come
along and start testing them. So we'll just expect the users to treat each
other respectfully and see how that works out" -- in which case it wouldn't
make sense to post a list of rules.
If you're feeling so inclined, you might bring this issue up for discussion
in the co-op conference.
-Valerie
At 11:39 PM 3/29/00 -0500, Kevin Nicholls wrote:
>
>I was not aware of this.
>Could you please tell me where I could find the AUP?
>
>On Wed, 29 Mar 2000, Valerie Mates wrote:
>
>> Twinkie, staff is getting a barrage of e-mail complaining about these:
>>
>> >Telegram from twinkie on ttyq6 at 20:21 EST ...
>> >Send your own masstels! Just type !./a/t/w/twinkie/masstel
>> >EOF (twinkie)
>>
>> Sending mass tels is not an acceptable use of Grex. Please stop.
>>
>> -Valerie Mates
>> Grex staff
>>
>> -------------------------------------------------------------------
>> Valerie Mates * Web Developer * http://www.valeriemates.com
>> valerie@cyberspace.org * (734) 995-6716
>> -------------------------------------------------------------------
>>
>>
>
>
>
-------------------------------------------------------------------
Valerie Mates * Web Developer * http://www.valeriemates.com
valerie@cyberspace.org * (734) 995-6716
-------------------------------------------------------------------
|
willard
|
|
response 51 of 163:
|
Sep 25 19:10 UTC 2000 |
Hahaha, Kevin, you crack me up.
|
bru
|
|
response 52 of 163:
|
Sep 25 20:33 UTC 2000 |
willard, you are making an ass of yourself. Not only are your actions wrong,
they are reprehensiblebecause you area a staff member on another system. They
don't allow these programs over there, why should they be allowed here. If
someone got into these programs and used the to damage the system, who do you
think would catch part of the responsibility?
Personally, I think they should do more. I think your account should be
deleted. You should be barred for a period of time. Yout position on M-net
should be revoked.
You are intentionally doing things to disrupt this system and they are being
more than tolerant of your activity. Maintainig it couldeven be considered
criminal if you keep pushing it.
|
willard
|
|
response 53 of 163:
|
Sep 25 23:23 UTC 2000 |
Hey Bruce, you wanna know what I think? I think you can go fuck
yourself. Good and hard. With a broomstick. That's what I think.
|
tod
|
|
response 54 of 163:
|
Sep 25 23:54 UTC 2000 |
So where is this AUP, anyhow?
|
danr
|
|
response 55 of 163:
|
Sep 26 00:08 UTC 2000 |
re #53: Mike, I don't think Bruce really gives a shit what you think. Nor do I.
We love you, but we wish you'd quit acting like such a baby.
|
willard
|
|
response 56 of 163:
|
Sep 26 00:10 UTC 2000 |
#55: You know what I think, Dan? I'll tell you. I think that as
soon as Bruce finishes with that broomstick, you should go for a
round.
|
jp2
|
|
response 57 of 163:
|
Sep 26 00:11 UTC 2000 |
This response has been erased.
|
russ
|
|
response 58 of 163:
|
Sep 26 01:52 UTC 2000 |
So let me get this straight. willard, who has made a point of
imposing on Grex's hospitality and everyone's patience and enjoying
every minute of it, is now breaking the rules of order on Grex... and
bragging about it?
willard is giving Grex a cause of action that has *nothing* to do with
his being the verbal equivalent of a diarrhetic bovine in the living room?
willard is practically *asking* to be thrown off, and this time in a way
that's actually likely to achieve it? And worst of all (for him), in a
way that leaves him with no grounds on which to honestly malign (as
opposed to abusing) Grex's commitment to free speech?
This is hilarious.
|
willard
|
|
response 59 of 163:
|
Sep 26 02:01 UTC 2000 |
I'm sorry.
|
keesan
|
|
response 60 of 163:
|
Sep 26 02:16 UTC 2000 |
Is it possible Willard is trying to be amusing, rather than abusing? I canot
imagine anyone keeping a straight face while making some of his statements.
|
twinkie
|
|
response 61 of 163:
|
Sep 26 03:21 UTC 2000 |
re: 58 -- I think the point willard is making, is that he's being punished
for a *very* stretched interpretation of a virtually nonexistent policy.
In a very real way, willard is being singled out. Whether he plays nice in
your sandbox is irrelevant. Correct me if I'm wrong, but isn't one of Grex's
purposes to promote learning Unix? Again, willard's knowlege of Unix is
irrelevant. It is not (or rather, should not be) the function of Grex staff
to determine who does, and does not "know" Unix. Nor should it be the function
of Grex staff to determine what is, and is not an acceptable compilation of
code, unless it's destructive to the system.
Certainly, one could argue that an idle killer is "destructive" in that it
means a marginally longer wait in the famed Grexqueue. But, does it completely
prevent people from using the system? More importantly, is there any scale
on which to guage exactly what kind of impact the program had?
That aside, calling a masstel script "destructive" is asinine to the nth
degree, unless this script is being used in such a way that Grex literally
becomes unusable. Inherently, it's not different from tel.
|
other
|
|
response 62 of 163:
|
Sep 26 04:24 UTC 2000 |
resp:42 lol
willard, you're pathetic. occasionally entertaining, too, but only when you
get pissy.
looking forward to the next installment. (who needs soap operas, anyway?)
|
janc
|
|
response 63 of 163:
|
Sep 26 04:41 UTC 2000 |
Willard is being singled out? How does treating willard exactly the
same way as hundreds of other users constitute "singling him out"? The
only thing that makes his case different is this item, which he started
himself.
And what have we done to him that is so horrid? Inserted messages into
his program telling him not to run such things on Grex. Wow, that's
cruel and unusual punishment, isn't it?
Sure we promote learning Unix here. One of the things we promote is
learning to share resources in a shared environment. A pretty
fundamental part of learning to use Unix, if you ask me.
True, Grex doesn't have an "acceptable use policy". Thats why, for
things that might not be completely obviously wrong we generally start
by telling the user this isn't acceptable. Putting messages into their
programs is an effective way to tell people this. (We got into this
habit because many of the people who come to Grex to "try out" various
annoying things don't give us their real email addresses and don't
bother to even look to see if they have mail on Grex. Putting a message
inside the program we don't want them to be running is a better way to
get through to them then sending them email.) We only nuke people
without talking first if they are doing pretty obviously nasty stuff -
fork bombs back when those actually worked, spamming, filling up the
disk, using Grex to try to crack other sites, etc.)
|
jerryr
|
|
response 64 of 163:
|
Sep 26 10:10 UTC 2000 |
y'all are having such a good time in this discussion, i really hate to insert
a question, but i would really like to know.
russ talks about grex' "hospitality" - doesn't everyone who creates a loginid
here have the same rights and resposibilities? or is there a class system
that i am unaware of - hosts and everyone else?
|