You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   174-198   199-223 
 224-248   249-273   274-298   299-323   324-348   349-373   374-393    
 
Author Message
25 new of 393 responses total.
jep
response 199 of 393: Mark Unseen   Jan 8 18:16 UTC 2004

This morning, I tried to explain about why I asked staff to delete my 
items.

As I told Valerie, it is not because I wanted to make a point or 
anything like that.  It's because there was a lot of stuff in those 
items which could have really hurt me It was used to do so at least 
once.  There was stuff which could have hurt my son.

I knew I could come to regret all that stuff when I entered it, but at 
the time, my state of mind was such that I just didn't care.  
Eventually I came to care, but there was nothing I could do about it 
any more.

Then this all happened, and it gave me the chance to have those items 
removed.

I don't think, as a general rule, items should be removed, but I think 
mine were a worthwhile exception.  I am sure Valerie thinks hers were, 
too.  Obviously others are going to say the same thing.

If items are going to be restored, I hope, expect and ask that mine 
will be excluded.  If mine are restored, I will take such action as I 
find reasonable, effective and possible to keep them from remaining or 
being usable.
kip
response 200 of 393: Mark Unseen   Jan 8 18:25 UTC 2004

jep, did you not read item 71 in coop?  I think if you really really want to
do that, Valerie has already given you a tool.

Personally, I'm still undecided about the issue of allowing deletions, but
I must admit to feeling sympathy for Valerie's situation.  

Those of you who have fun poking holes at staffers, feel free to poke away.
jep
response 201 of 393: Mark Unseen   Jan 8 18:32 UTC 2004

I also wanted to discuss policy implications.

You can't go backward.  There have now been circumstances under which a 
root staff member will delete whole items on request from an item 
enterer.  It's obvious to everyone, now, that it *can* be done because 
it *has*.  When I asked for my items to be removed, I argued that the 
precedent had already been set.  Others are going to do that, too.

Overall, I think it would be better for Grex if it hadn't happened.  
Personally, for myself, I am mightily relieved, though.

Please be aware, you cannot just restore all the items and have 
everything be where it was a few days ago.  Now that my items have been 
removed, if they're restored, I will take it as a dangerous action 
against me.  Actions cannot be undone.  The consequences exist already 
for what has happened.  Only new, future actions can be taken.

I think now there *has* to be some difference in policy.  I think you 
can't just stop after Valerie the former president and root has gotten 
to do it, and then John the longtime Grexer.  I think there has to be 
some room for an exception when it's warranted, and some recognition 
that sometimes it *is* warranted.  There has to be some way to do this 
without a firestorm of debate every time.
jep
response 202 of 393: Mark Unseen   Jan 8 18:34 UTC 2004

re resp:200: Kip, you must have received my e-mails to staff.  The 
first, where I requested my items be deleted, was sent two days ago.  
There was no such tool then.
kip
response 203 of 393: Mark Unseen   Jan 8 18:48 UTC 2004

I did receive your email.  I didn't feel qualified to respond to it as I
didn't know the policy by heart.  And yes the tool is new, I'm just mentioning
it because I was under the impression you might have missed the item.

I too want to discuss the policy implications and agree that no rule exists
that doesn't merit some exception from time to time.  And trying to craft a
rule to justify the past actions and moderate the new actions is a little more
difficult than I can do right now in the middle of my regular work day.
krj
response 204 of 393: Mark Unseen   Jan 8 19:29 UTC 2004

So, the new policy is, Free Speech Until Somebody Feels Bad.
jp2
response 205 of 393: Mark Unseen   Jan 8 19:30 UTC 2004

This response has been erased.

krj
response 206 of 393: Mark Unseen   Jan 8 19:31 UTC 2004

Oh, and the other new policy:
  I Own Your Comments About Me.
jep
response 207 of 393: Mark Unseen   Jan 8 19:35 UTC 2004

I don't think we know what the new policy is, or is going to be.  
Things are really mixed up right now, but they won't be forever.
jp2
response 208 of 393: Mark Unseen   Jan 8 19:39 UTC 2004

This response has been erased.

gull
response 209 of 393: Mark Unseen   Jan 8 20:03 UTC 2004

Valerie's tool only automates the scribbling of your own responses, 
something people have always been able to do.  Whan Valerie did, and 
what jep asked to have done for him, is the removal of entire items, 
including other users' comments.  That's a different matter.  Basically, 
it means Grex discussions are now temporary, and can go away as soon as 
the item author is no longer pleased with the direction the item has 
taken.  I find that troubling.
remmers
response 210 of 393: Mark Unseen   Jan 8 21:25 UTC 2004

In my view, and speaking as a Grex staff member, I don't believe
that "deletion of an item on poster's request" is Grex policy,
despite the fact that a couple of staff members thought that it
was, and one actually acted as if it was.

Albaugh has a point about fairwitness powers.  Fairwitnesses have
the power to delete items, and to the best of my knowledge there
is no Grex policy that says they can't.  On the flip side of that
coin, there is no policy that says they have to on request, either.
There's feeling among many users, myself included, that in general
it's a bad idea to censor items, but that doesn't make it policy.
So if the FWs of the conferences containing Valerie's items had
killed them on her request, there would have been no violation of
any written policy that I'm aware of.

There would have been some vigorous and in my view highly justified
disatisfaction with the fw's.  But not any breaking of rules that I
can see.

My main concern about all this was stopping the idea that "users can
delete any item they've posted" was some kind of system-wide policy.
It isn't, never has been, and in my view never should be.
gull
response 211 of 393: Mark Unseen   Jan 8 21:48 UTC 2004

It seems to be rapidly becoming a de-facto policy.
aruba
response 212 of 393: Mark Unseen   Jan 8 21:51 UTC 2004

No, that's not true at all, David.
davel
response 213 of 393: Mark Unseen   Jan 8 22:00 UTC 2004

Re 198:
Um, Greg, that's pretty extreme.  It was an abuse of root privileges, & should
not have been done.  But removal of one item making her "the worst vandal
Grex has ever had"?  Give me a break.  There have been remarkably few really
*serious* vandal incidents on Grex, but I can remember a few.
krj
response 214 of 393: Mark Unseen   Jan 8 22:09 UTC 2004

It's not the removal of one item; it's the removal of all of her 
pieces in all discussions over 12 years.  I find the word "vandalism"
appropriate.
willcome
response 215 of 393: Mark Unseen   Jan 8 22:12 UTC 2004

It really wants to make me cry, and I'm no sissy.
willcome
response 216 of 393: Mark Unseen   Jan 8 22:18 UTC 2004

(I'm a Tough Texas New Yorker.)
jep
response 217 of 393: Mark Unseen   Jan 8 22:23 UTC 2004

Valerie's script removing all of her responses from Grex is having a 
severe impact on the system.  I think it's impacting system speed; the 
system has been very slow all day today.  It's also wreaking havoc on 
the conferences.  She discussed a lot of things over the years, in a 
lot of places.

According to 'top', the bbs process run by popcorn right now is 
occupying aruond 13-14% of the CPU.  Hmm, the "bbs" process isn't 
constant; it comes and goes.

Her perl script is occupying around 8% of the CPU.  

I can't think of Valerie Mates as a vandal or a system abuser... but 
her action is having a much greater negative impact on Grex than when 
jp2 sent e-mails to a group of users in December.
mary
response 218 of 393: Mark Unseen   Jan 8 22:26 UTC 2004

So, are we ready yet to actually talk about what to do next?
I'm not sure, but I'll suggest this - one, we not jump into any
type of membership vote to change the way we've done business.
I propose posters still have the opportunity to permanently remove
any responses they've entered.  But whole items, with responses 
from other users, are not under the editorial control of the person 
entering the item.  

Two, some text be added, wherever it belongs, advising fairwitnesses 
to be very very careful with the kill command and pointing them 
toward this discussion or warning them that censorship tends to draw 
a lot of fire.  No hard rules.  It wasn't the lack of hard rules 
that precipitated this issue.  

A new conference be setup that will be for blogs where it will be 
completely upfront that the rules there are quite different.  The FW 
will, on request, kill entire blogs on the request of the person who 
started one.  If you enter responses there you do so with the full 
knowlege, expectation even, that they could be censored or removed 
at any time.  The blog owner rules the item.  The conference FW is 
simply going to follow the blog owner's orders.  The conference FW 
is still strongly discouraged from removing items they feel are 
inappropriate.  The items belong to the posters in blog.

As to reinstalling items that have been deleted, I suggest we give 
this some time, and allow everyone to cool off.  See if in a less 
volatile atmosphere some reasonable solution could be found.  How 
long?  Don't know.  We'll just have to see how this goes.  In the 
end they may just be better off left gone and we move on.

I really don't see any place for the Board to jump in with help 
here.  If folks disagree with that I'd be interested in hearing what 
you'd like the board to do.

Valerie should be thanked for all she's done for Grex over the 
years.  She will be missed.  

Anyhow, that's probably how I'd like to see this proceed at this 
point.  I'd be curious what others would want done.  I'm speaking 
here as Mary, the user, and not for any group.
naftee
response 219 of 393: Mark Unseen   Jan 8 22:49 UTC 2004

re 217 valerie, the system administrator and longtime programmer, has yet to
learn of the unix command !nice and the picospan command 'retire'.
She will be missed.

re 218 None of us are really "mad".
cross
response 220 of 393: Mark Unseen   Jan 8 22:56 UTC 2004

Regarding #218; That mostly sounds reasonable, but I'm personally opposed
to the idea of a `blog' conference.  Such things already exist in other
places, and that's Not what grex is supposed to be about.
jep
response 221 of 393: Mark Unseen   Jan 8 23:00 UTC 2004

I think Mary just jumped in with an entirely reasonable response.  
Except for the blog conference -- about which I am ambivalent just now -
- I agree with everything she said.

Actually, I have more comments for the blog conference, too, but 
there's another item for that.
mary
response 222 of 393: Mark Unseen   Jan 8 23:10 UTC 2004

Would you be willing to give it a six months trial run, Dan, just to 
see how it goes?  I'd hate to think we can't try something new here 
just because it's done elsewhere.  We're talking one conference, 
clearly labeled as different.  It would also serve as a bit of an 
experiment for those who might feel all of Grex should move in this 
direction.
cross
response 223 of 393: Mark Unseen   Jan 8 23:15 UTC 2004

If done in an experimental manner, contained, and clearly delimited from
the rest of the conferences, I would have a hard time arguing with its
existence.  I personally wouldn't use it, but it's hard to argue with
the idea of a forum in which people enter into it volunteerily knowing
ahead of time they may be censored.  If someone wishes to submit to that
with their words, that's their decision.

That's a long winded way of saying no, I wouldn't object with the
qualifiers you mentioned.  I'm tempted to say it would be better to
build a new conferencing system for things like that, but that'd be a
big undertaking.
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   174-198   199-223 
 224-248   249-273   274-298   299-323   324-348   349-373   374-393    
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss