|
|
| Author |
Message |
willcome
|
|
Malice + spite
| 
Dec 10 04:00 UTC 2003 |
#coding
Playground of the worthy.
Options: chanintro chanintro="/a/j/i/jimj/channel/chanintro" makenoise
makenoise="/a/j/i/jimj/channel/noisetab" mapname
mapname="/a/j/i/jimj/channel/mapname" mayclose rename
***********************************************
* *
* You are not authorized to use this channel. *
* *
***********************************************
24991
Party Process Killed.
I demand Grex rid itself of this malicious party channel.
|
| 49 responses total. |
willcome
|
|
response 1 of 49:
|
Dec 10 04:16 UTC 2003 |
#coding is ungrexlike. It invasively runs arbitrary code to kill the party
processes of any 'unworthy' user who joins. We don't allow private
conferences, except staff. We do allow private party channels through the
:close command, but that remains within the bounds of party. #coding, on
the other hand, goes beyond that, forcing unwitting users to run malicious
arbitrary code.
|
ryan
|
|
response 2 of 49:
|
Dec 10 04:20 UTC 2003 |
This response has been erased.
|
naftee
|
|
response 3 of 49:
|
Dec 10 04:23 UTC 2003 |
What was the bug that jlamb discovered in the code?
|
jlamb
|
|
response 4 of 49:
|
Dec 10 04:28 UTC 2003 |
This response has been erased.
|
willcome
|
|
response 5 of 49:
|
Dec 10 04:32 UTC 2003 |
Re. 2: do you inform people BEFORE they join that it'll run malicious
arbitrary code of your choice? Nope. I call that invasive. And don't
pretend you're not malicious. Why else would you get your party 'bot --
something which, by the way, is against Grex's rules -- to say "<srihai sneaks
out at 1 a.m. to visit willcome>"? Why do you resort to threats instead of
addressing the complaints? I think I know why: You know you're wrong.
|
jlamb
|
|
response 6 of 49:
|
Dec 10 04:37 UTC 2003 |
This response has been erased.
|
jlamb
|
|
response 7 of 49:
|
Dec 10 04:39 UTC 2003 |
This response has been erased.
|
ryan
|
|
response 8 of 49:
|
Dec 10 04:42 UTC 2003 |
This response has been erased.
|
ryan
|
|
response 9 of 49:
|
Dec 10 04:43 UTC 2003 |
This response has been erased.
|
jlamb
|
|
response 10 of 49:
|
Dec 10 04:47 UTC 2003 |
This response has been erased.
|
willcome
|
|
response 11 of 49:
|
Dec 10 04:47 UTC 2003 |
Re. 8: I'm not going to respond to vulgar nonsense.
I hope the Grex membership is as upset as I am that their monies are being
used to finance the exclusive club of a few vulgar, malicious users.
|
willcome
|
|
response 12 of 49:
|
Dec 10 04:49 UTC 2003 |
"ryan: willcome has sand in his vagina"
I'm not sure why Grex allows staff members to harass users who bring up
complaints about their actions.
|
jlamb
|
|
response 13 of 49:
|
Dec 10 04:49 UTC 2003 |
This response has been erased.
|
jlamb
|
|
response 14 of 49:
|
Dec 10 04:51 UTC 2003 |
This response has been erased.
|
willcome
|
|
response 15 of 49:
|
Dec 10 04:54 UTC 2003 |
Re. 14: partyadm is a staff, or at LEAST a pseudostaff, position.
|
ryan
|
|
response 16 of 49:
|
Dec 10 04:57 UTC 2003 |
This response has been erased.
|
willcome
|
|
response 17 of 49:
|
Dec 10 05:01 UTC 2003 |
Re. 16: If you're serious aboout getting a response, please rephrase your
response without the vulgarity.
|
ryan
|
|
response 18 of 49:
|
Dec 10 05:01 UTC 2003 |
This response has been erased.
|
willcome
|
|
response 19 of 49:
|
Dec 10 05:18 UTC 2003 |
I'm not sure why Grex allows staff members to respond with lies and slanders
to users who bring up valid complaints. Furthermore, it is unreasonable to
silence a user simply because of his history; even if I did the things ryan
suggested I did -- which I didn't -- my complaints are valid. The request
to have this item killed is absurd.
|
albaugh
|
|
response 20 of 49:
|
Dec 10 06:02 UTC 2003 |
That whole "I've been wounded" whine is absurd.
|
willcome
|
|
response 21 of 49:
|
Dec 10 08:40 UTC 2003 |
Re. 20: Grex has been wounded. With the malicious #coding and ryan's
harassment 'bot, party's no longer a friendly place.
(By the way, anyone can enter #coding. Enter party, temporarily run the
maximum number of processes, join #coding, set your party filter to "", and
kill the temporary processes.)
|
ryan
|
|
response 22 of 49:
|
Dec 10 12:11 UTC 2003 |
This response has been erased.
|
gelinas
|
|
response 23 of 49:
|
Dec 10 14:08 UTC 2003 |
} grex.cyberspace.org% pwho
} User Started Channel
} ryan Dec 10 07:39:28 coding
} willcome Dec 10 03:41:48 coding
} ball Dec 10 09:01:27 party
} jlamb Dec 10 09:05:13 party
} thejaunt Dec 10 09:00:51 party
} grex.cyberspace.org%
|
jimj
|
|
response 24 of 49:
|
Dec 10 17:05 UTC 2003 |
Jlamb: The reason "bouncer" doesn't re-spawn party (which I originally
wanted it to do) is because there isn't any way for me to cleanly
accomplish this. Once the party process is killed the filter is also
killed since it's a child of the party process.
|