HDTenEightyP/NetNews huggingface dataset:
From: schuetz@fm11ap01.tu-graz.ac.at (Alexander Schuetz)
Subject: sorry another new user
Organization: none
Date: Wed, 16 Dec 92 10:26:13 GMT


hi all sorry to bother you but i am a new user. What *is* IRC and how 
do I get there right from Internet? I only know how to Email, how to FTP and 
how to write articles in a newsgroup. 
(Yes I also know the netiquette and what a FAQ is but....). 
please email to "schuetz@fm11ap07.tu-graz.ac.at". thanks. alex.



Newsgroups: alt.irc
From: visit1@iscs.nus.sg (Herman H. Fredriksson)
Subject: Re: A new (very simple) bot solution
Reply-To: VISIT1@NUSDISCS.BITNET
Organization: Dept. of Information Systems and Computer Science, National University of Singapore
Date: Tue, 15 Dec 1992 02:53:08 GMT

avalon@coombs.anu.edu.au (Darren Reed) writes:
>evansmp@uhura.aston.ac.uk (Mark Evans) writes:
>
>>-b *!*@* removing all bans would also make sense.
>
>Then how do you remove "*!*@*" if someone adds it via a +b command ?
>(And that is the *only* one you want removed).  Its simple how it is
>now, making it more complex will not help (esp. if people are putting
>\'s in for some dumb reason).

under such a system, if you have a mode "+b *!*@*" it would be the
*only* ban there, since it would replace any other bans on the channel,
so of course it would be the *only* one you want removed...

>avalon

herm

-- Herman H. Fredriksson ------------ <visit1@vms1.iscs.nus.sg> ------
-- On Holidays in -------------------- <herm@coombs.anu.edu.au> ------
-- National University of Singapore ----- <herm@nitha.etsu.edu> ------
-- Republic of Singapore ---------------------------------------------
Newsgroups: alt.irc
From: cc4507@u.cc.utah.edu (Chucki Carpinello)
Subject: Re: patriot.mit.edu (vanity server alert)
Organization: University of Utah Computer Center Student Mail Machine
Date: Fri, 18 Dec 92 11:51:08 GMT

In article <1992Dec18.044353.29301@rat.csc.calpoly.edu> asamonte@polyslo.csc.calpoly.edu (Just some loser...) writes:
>tjm@hrt213.brooks.af.mil (Tim Miller) was telling me...
>>On Thu, 17 Dec 1992 16:16:50 GMT, mnystrom@athena.mit.edu (Mika Nystroem) said:
>>
>> M> I haven't fixed it because I don't have root access and the people who do aren't
>> M> going to. I did the following instead:
>>
>> M> [from /scratch2/mnystrom/ircd.conf]
>>
>> M> K:patriot::*
>> M> K:localhost::*
>>
>> M> So now we get:
>> M> *** Connecting to port 6667 of server patriot
>> M> *** *** Ghosts are not allowed on IRC.
>>
>> M> I hope everyone is satisfied. 
>>
>>	Hardly.  Take it out.
>>
>>	Why should you disallow user on the host local to the server
>>simply because some loser decides that it offends his sensibilities?
>>Particularly when he's dunce enough to call a *system* problem an *IRC*
>>hack.
>
>I agree, K lining your own host is kinda silly.  All you ahve to do is have them fix
>the problem.  But you're too lazy to ask them, or motivate the admins to do it.
>

You are the one who pressured him to do it.. You make no sence   


-- 
Chucki Carpinello
__
\/	Chucki.Carpinello@M.CC.Utah.EDU
Newsgroups: alt.irc
From: cc4507@u.cc.utah.edu (Chucki Carpinello)
Subject: Re: patriot.mit.edu (vanity server alert)
Organization: Yo Man!
Date: Thu, 17 Dec 92 02:38:59 GMT

In article <mrgreen.724462764@munagin> mrgreen@mullian.ee.mu.OZ.AU (matthew green) writes:
>mnystrom@athena.mit.edu (Mika Nystroem) writes:
>
>>In article <1992Dec14.103032.563@rat.csc.calpoly.edu>, asamonte@polyslo.csc.calpoly.edu (Just some loser...) writes:
>>|> How about a server that fakes host names for people?  Do you know of
>>|> many other servers that do that?  Gee mnystrom@patriot  what the hell
>>|> kind of address is that?
>
>>Well, it certainly isn't *fake*, although it may be a little incomplete. :)
>>You can get almost any server to do something similar to a hostname almost 
>>as simply as patriot. Try /server localhost sometime while you're running 
>>a client on your favorite server computer. Most servers I have seen do not 
>>have K-lines for "* localhost". 
>
>At least when you /server localhost, the whole domain comes up..
>
>311 p is mrgreen@localhost.ee.mu.OZ.AU (the lame one, also monica's)
>312 on irc via server munagin.ee.mu.OZ.AU (University of Melbourne, Australian Hub)
>317 p has been idle 0 seconds
>
Not always. . .
*** Chucki is chucki@localhost (Chuck Carpinello)
*** on IRC via server csulx.weber.edu (Weber State college, Odgen, Utah)
*** Chucki is not idle

>Any one with any clues will know that you are on the machine the server
>is running on.  As to just showing user@host but no domain, when there are
>machines with the same first name around..  tsk tsk..  and there are two
>American servers with that are called uxa.  Cool.
>
>
say YES to non-local oper kills with harsher punishments


-- 
Chucki Carpinello
__
\/	Chucki.Carpinello@M.CC.Utah.EDU
Newsgroups: alt.irc
From: mrgreen@mullian.ee.mu.OZ.AU (matthew green)
Subject: Re: yes or no? (bot deopping)
Organization: Computer Science, University of Melbourne, Australia
Date: Tue, 15 Dec 1992 08:26:06 GMT

titus@coombs.anu.edu.au (titus chiu) writes:

>gl8f@fermi.clas.Virginia.EDU (Greg Lindahl) writes:
>>I think that all your solution would do is result in an explosion of
>>number of servers, server operators, and kills.

>why dont we just get rid of modes altogether :*) ... and have negative
>channels back :*) (without mode command to -s it i guess) .. as for
>kicks .. that really isnt necessary with the advance ignore command of
>the ircII clients nowadays.. is it?

Yup, with ignore, KILL and to a less degree, KICK, are becoming redundant.

[ ... ]

>>seconds? Does anyone think IRC would be less useful with a strict rate
>>limit on nick, topic, and join?

>well... i doubt nick and topic msgs need to be issued in quick successions
>in any normal use.. as for join.. well.. the only problem i c if join
>command is subjected to flood control is for people who join a few channels
>in their .ircrc and it will slow them down a little..

Whats wrong with 

join #one,#two,#three,#four,#five,#six

??  If you make the server only take that as one message from the client
(unlike privmsg), then you don't turn on flood control.

phone..

say NO to non-local operator KILLS..
Newsgroups: alt.irc
From: buboo@alf.uib.no (Ove Ruben R Olsen)
Subject: Re: Whereis the MiniIRC client??
Organization: University of Bergen, Norway
Date: Tue, 15 Dec 92 17:20:37 GMT

Tim Miller writes:

>	How small is small?  Rocker's elisp irc client is 104K
>byte-compiled, and I've got a working (albeit *VERY PRIMITIVE*) working
>elisp client core that's just over 2K.

I got a perlclient that is aprox 1100 bytes big...

The Working Perl Client (The Princess Client) as it is now, goes into
63142 bytes. It's only a beta release, but it works... :-)

\Ruben.

-- 
        Ove Ruben R Olsen a Gnarfer and VI user. EMAIL: ruben@uib.no. 
     Maintaining the EX/VI-archive and a couple of the Comp.Editors FAQs.
    People that are ignorant tend to live a frustrated life, at least when 
     it comes to editing - But I do belive this is a general rule in life
Newsgroups: alt.irc
From: mstieb@nyx.cs.du.edu (Michael Stieb)
Subject: Home Machine kicks me off
Organization: Nyx, Public Access Unix @ U. of Denver Math/CS dept.
Date: Sat, 19 Dec 92 05:01:30 GMT


  Well, I really enjoy IRC.  However, my home machine( not NYX) kicks me
off of any server that I connect to.  I get an "access violation" msg
followed by a stack dump.  Sometimes I can use it for a week before some
system admin or a program on my home VAX notices and kicks me out.  Any
suggestions?  Does any of the internet BBSs allow irc client servers to be
run or am I just out of luck?
  This may be a long Christmas Break without IRC!

Standard Disclaimer Here (I'm not clever enough to write my own)
Stieb@outlaw.uwyo.edu
From: gwydion@hal.gnu.ai.mit.edu (Mercenary Programmer)
Newsgroups: alt.irc
Subject: Re: patriot.mit.edu (vanity server alert)
Date: 16 Dec 1992 02:28:22 GMT
Organization: /etc/organization
NNTP-Posting-Host: hal.gnu.ai.mit.edu

In article <1992Dec15.014934.16284@rat.csc.calpoly.edu> asamonte@polyslo.csc.calpoly.edu (Just some loser...) writes:

>It's fake to me.  host patriot doesn't give me anything a nic.ddn.mil whois
>of patriot doesn't help either  I don't care what kind of stupid justification
>you use.  All you are doing is inviting other people do to the same, soon the
>boundaries are stretched and then who knows what.  You KNOW you're faking
>your host.  Why do you have to do it?  Is there any particular reason?
>No, I don't think so. 


> finger mnystrom@patriot
[patriot.mit.edu]
Login name: mnystrom                    In real life: Mika Nystroem
Phone: W7-335, 2257335
Directory: /mit/mnystrom                Shell: /bin/athena/tcsh
Last login Tue Dec 15 19:44 on ttype from RAVIOLI.MIT.EDU
Project: Got started!
No Plan.
> exit

Get a clue.
The rest is left to the loser as an exercise.

Gwydion.
Newsgroups: alt.irc
From: tjm@hrt213.brooks.af.mil (Tim Miller)
Subject: Re: patriot.mit.edu (vanity server alert)
Followup-To: dev.null
Organization: AL/HRTI, Brooks AFB
	<1992Dec11.155558.2035@murdoch.acc.Virginia.EDU>
	<1gbjbpINNjr2@life.ai.mit.edu>
	<1992Dec12.050054.16142@murdoch.acc.Virginia.EDU>
	<1992Dec13.234905.29558@athena.mit.edu> <avalon.724312284@coombs>
Date: Tue, 15 Dec 1992 14:06:07 GMT

On 14 Dec 92 05:51:24 GMT, avalon@coombs.anu.edu.au (Darren Reed) said:

 > but if gwydion is an oper on that server, its at least 1 line too long.

	In the same vein of loving-kindness:

	But if Avalon exists as a person, that's one person too many.

-- Cerebus <tjm@hrt213.brooks.af.mil>
"Followup-To: dev.null
From: asamonte@polyslo.csc.calpoly.edu (Just some loser...)
Newsgroups: alt.irc
Subject: Re: patriot.mit.edu (vanity server alert)
Date: 16 Dec 92 19:37:15 GMT
Organization: Nothing worth mentioning...

tjm@hrt213.brooks.af.mil (Tim Miller) was telling me...
>On 15 Dec 92 20:29:23 GMT, asamonte@polyslo.csc.calpoly.edu (Just some loser...) said:
>
> > People have explained possible reasons.  But seems to me that since it
> > HASN'T been fixed, then I consider it a hack...how long has patriot
> > been up?  I haven't kept track...but it's been a while.  He knows
> > the problem exists, so why has nothing been done to fix it?
>
>	I'll tell you why: because if it doesn't break sendmail (i.e.,
>the domain is stamped by the mailserver so that a recipient can directly
>reply to a mailing from that machine) it just isn't a high priority to
>fix.  The only reason I fixed it here is because my braindead mailserver
>*doesn't* stamp domains properly on outgoing mail.

And how do you know patriot would be any different.  According to what
has been said it hasn't even been attempted to fix, so how are you going
to know it's gonna break other things?
> > Oh, a few days, a week...Well atleast you're expedient in fixing it.
> > From mystroms post, he did not see it a a problem, nor did he show
> > any indication of wanting to fix it.
>
>	Why screw with what ain't broken?  I've done enough of that to
>know it usually breaks something else that's more critical.

Oh I see, you wouldn't consider it broken huh?  Maybe a feature?  Doubtful.
I wouldn't say it's working as it should.

-Alex

--
From: avalon@coombs.anu.edu.au (Darren Reed)
Newsgroups: alt.irc
Subject: Re: Protecting privacy of users against IRCops; making umode +i effective.
Date: 18 Dec 92 02:58:01 GMT
Organization: Australian National University
NNTP-Posting-Host: 150.203.76.2
Keywords: invisibility privacy and IRCops

hachec@ERE.UMontreal.CA (Greg Patterson) writes:

>In article <1g35s9INN9vg@manuel.anu.edu.au> titus@coombs.anu.edu.au (titus chiu) writes:

>>Nicolas.Pioch@grasp.insa-lyon.fr (Nicolas Pioch) writes:
>>>not theirs. This means reducing the output of /trace and /stat l commands
>>>to server-related infos only for foreign IRCops. Here are the patches:
>>>send flames to the usual place...
>>
>>isnt this bordering on server hacking to not display trace and stat l 
>>information? or doesnt anyone care about server integraty anymore?

>I can't wait till a few abusive users come across a server with this hack.
>Can we say: Flood and Hide, Flood and Hide, Flood and Hide...

They wont be flooding.
From: avalon@coombs.anu.edu.au (Darren Reed)
Newsgroups: alt.irc
Subject: Re: A new (very simple) bot solution
Date: 20 Dec 92 07:30:24 GMT
Organization: Australian National University
NNTP-Posting-Host: 150.203.76.2

mattm@digex.com (Matt Mosley) writes:

>>under such a system, if you have a mode "+b *!*@*" it would be the
>>*only* ban there, since it would replace any other bans on the channel,
>>so of course it would be the *only* one you want removed...

>Actually, this really should be done.  A "+b *!*@*" should replace all
>other bans, and remove them.  Same thing with "+b *!*@my.host.edu" removing
>"+b *!*@*.host.edu" ... it's called redundancy, folks.

but which is lexically greater/less than the other for this ?

avalon

say no to .. ummm...fascists!
Newsgroups: alt.irc
From: gl8f@fermi.clas.Virginia.EDU (Greg Lindahl)
Subject: Re: patriot.mit.edu (vanity server alert)
Organization: Department of Astronomy, University of Virginia
Date: Fri, 11 Dec 1992 21:07:26 GMT

In article <1992Dec11.194808.26570@njitgw.njit.edu> lcm1501@hertz.njit.edu (Lawrence C. Mc Abee) writes:

>	patriot.mit.edu is not a vanity server.

... in your opinion. you'll be happy to know that irc.mit.edu is
being upgraded to a real machine soonish, so cpu will no longer be a
problem for it (not that it's really CPU bound...)


Newsgroups: alt.irc
From: jedubins@unix.amherst.edu (Just a fellow traveller...)
Subject: One channel one channel op.
Organization: Limbo, Org.   (how low can you go)
X-Newsreader: TIN [version 1.1 PL7]
Date: Tue, 15 Dec 1992 04:01:54 GMT

If the problem is how to deal with a channel when the one channel op
leaves, why not institute an automatic kick for everyone on the channel?

You would have to be sure a connection was established with the ops 
server first, as to be sure that therre hadn't been a netsplit, but
otherwise, might it not work, with a few modifications?

One modification might be to make it so the previous channel-op had to wait
longer to rejoin the channel than the others- so that in effect he couldn't
do an automatic kick of everyone around without losing the chance of
getting the channel op back for him/herself.
From: gwydion@gnu.ai.mit.edu (Mercenary Programmer)
Newsgroups: alt.irc
Subject: The IRC router's Lament
Date: 12 Dec 1992 12:40:42 GMT
Organization: MIT Artificial Intelligence Lab
NNTP-Posting-Host: wookumz.gnu.ai.mit.edu
Attributed-To: Andrew K Bressen <bressen@ground.cs.columbia.edu>
Originator: gwydion@wookumz.gnu.ai.mit.edu

   	To route, or not to route; that is the question:
   	Whether 'tis nobler on the net to suffer
   	The pings and arpage of outragous contention,
   	Or to make greps against a sea of packets,
   	And, by subnetting, end them. FDDI, to bus
   	No more, and by a ring to say we end
   	The collisions and the thousand packet drops
   	That CSMA is heir to 'tis a consummation
   	Devoutly to be wished. FDDI, token ring.
   	Token ring, perchance to DQDB. Ay, there's the rub,
   	For that speedy net where ATM may come
   	When we have shuffled off to double coils
   	Might give us loss. There's the respect
   	That makes calamity of systems implementation,
   	For who would bear the whips and scorns of irate users,
   	Th'parameters' wrong, LanMan's contumely,
   	The pangs of vaporware, the CCITT's delay,
   	The insolence of Microsoft, and the spurns
   	That patient network managers of th'unworthy takes,
   	When he himself might his quietus make
   	With a bare wire? Who would these fardels bear,
   	To grunt and swear at border gateway protocol
   	But that the dread of OSI,
   	The undiscovered country from whose bourn
   	No traveller returns, puzzles the will,
   	And makes us rather bear those ills we have
   	Than fly to others that we know not of?
   	Thus banyans do make switches of us all,
   	And thus the native queue of transmission
   	Is cycled over with the subnet casts of MOP,
   	And enterprise architectures of many bits and SONET
   	With this regard the carriers turn awry,
   	Because they push SMDS. Software, now,
   	The fair Sybase 4.8A! dbtemp, in thy horizons
   	Be all my sins renumbered.


Newsgroups: alt.irc
From: Sten M. Drescher <smd@hrt216.brooks.af.mil>
Subject: Re: yes or no? (bot deopping)
Organization: AL/HRTI, Brooks AFB
	<1gm39aINN9ee@life.ai.mit.edu> <avalon.724659914@coombs>
Date: Fri, 18 Dec 1992 19:47:39 GMT

On 18 Dec 92 06:25:14 GMT, avalon@coombs.anu.edu.au (Darren Reed) said:

># Consider the recent case where person Page (an operator) was killed
>by # person SpUr (another operator) who was then killed by person
>Gwydion # (another operator) and to end it all, person SpUr then
>squit'd the # server that person Page was on.

Gwydion>At no point did I kill SpUr, as you have claimed.

 Darren> Read it again.  No such claim was made.

	I read it again.  It says SpUr killed Page,  Gwydion killed
SpUr, SpUr squitted Page.

 Darren> Maybe you got your
 Darren> pronouns mixed up, Page was the subject of the first sentence
 Darren> and to which the "who" is refered to.  But that is just a
 Darren> trivial point.  If my grammar is lacking and I've got it wrong
 Darren> then I'll rewrite it for you:

 Darren> Page killed Spur (stupid reason); Gwydion killed Page for
 Darren> killing Spur (another stpuid reason); Spur squits the server
 Darren> Page is on (the most stupid reason of the three).

	NOW you're not saying that Gwydion killed Page.  It looks like
YOU confused yourself with the 'was killed by' construction.
From: Nicolas.Pioch@grasp.insa-lyon.fr (Nicolas Pioch)
Newsgroups: alt.irc
Subject: Re: Protecting privacy of users against IRCops; making umode +i effective.
Date: 12 Dec 1992 17:12:59 +0100
Organization: Bandits de Grand Chemin Corp. Unltd
Distribution: world
NNTP-Posting-Host: grasp1.univ-lyon1.fr
Keywords: invisibility privacy and IRCops

Quoting gl8f@fermi.clas.Virginia.EDU (Greg Lindahl):
 -> male operators who are harrassing female users generally know what
 -> server the target uses.

Precisely. If someone wants to disappear from a lamer's eye, using
umode +i he just needs to /nick something else... but this doesn't work
for an IRCop who can still /trace the server and find out the new
nickname in use...

The only way is to switch server too... you wouldn't want people from
an university with an ircd server running to log on another server
a few thousands kilometers away only to get rid of a jerk, would you ?

Given the fact that WHOWAS allows you to get the user@host of anybody
annoying you in order to set up an IGNORE, that KILL has a built-in
tracking feature to get rid of renicking clients, and that K: lines
should be used more often, are there any *good* reasons left not to
include these changes in the next server release ?
Maybe this should be changed in order to hide umode +i users only
as Avalon suggested.

By the way, while I'm at it, there was a little confusion in my patches
between Local Operators and IRC Operators that are local clients...
(in the /stat l patch) so here are the good changes to be made:

in ircd/s_msg.c
around line 2210,  (IsOper(sptr) || !IsPerson(acptr) ||
should become      ((IsOper(sptr) && (MyClient(sptr))) || !IsPerson(acptr) ||
and
around line 3153,  if (IsOper(sptr)) /* Only opers see users */
should become      if ((IsOper(sptr)) && (MyClient(sptr))) /* Only local-ops */

Remember, programming is fun, irc'ing is lame ;)

-- 
*** Nicolas
    E-Mail: Nicolas.Pioch@grasp.insa-lyon.fr      (pioch@poly.polytechnique.fr)
    IRC:Nap   >>> HAPPY user of OS/2 version 2.01, switching to NT next march !
From: asamonte@polyslo.csc.calpoly.edu (Just some loser...)
Newsgroups: alt.irc
Subject: Re: patriot.mit.edu (vanity server alert)
Date: 19 Dec 92 04:01:37 GMT
Organization: Nothing worth mentioning...

Sten M. Drescher <smd@hrt216.brooks.af.mil> was telling me...
>
> Just> Sure it does.  Or atleast it doens't work as it should.  WHenever
> Just> someone tries to forge a usenet posting, that's considered a
> Just> hack.  I see irc as following the same rules.  When this was a
> Just> hot topic a year or so ago about forged usernames, someone cited
> Just> some net policy about misrepresenting yourself or something.  If
> Just> such a policy exists, I would think it would apply here too.
>
>	OK, MilNet 'policy' is to refuse to allow reverse resolving.
>Therefore, whenever I go onto IRC, I show up as smd@140.140.4.216,
>arather than smd@animal.brooks.af.mil or smd@hrt216.brooks.af.mil.  I
>can't fix this, neither Cerebus nor I have enough pull to get it fixed
>(and A1C and a Sgt vs. MilNet admin - yeah, right!).  How long's it
>gonna be before I'm accused of forging my location?  Don't worry, I
>already have been, and Cerebus only introduced me to IRC a month ago.

smd@140.140.4.216 is a valid address...I can mail there, i can traceroute
to there..
If your whois said smd@140   I woudl then have a problem.
(Though smd@216 would probably be more 'correct' in comparison to patriot)

-Alex

-- 
Newsgroups: alt.irc
From: jnelson@iastate.edu (Jeremy F Nelson)
Subject: Re: Whereis the MiniIRC client??
Organization: Iowa State University, Ames, IA
Date: Wed, 16 Dec 1992 00:58:34 GMT

> I heard around the traps of a MiniIRC, TinyIRC client??

>
>This one is perhaps even more primitive, but working anyway:
>
>#!/bin/sh
>telnet your.server.wherever 6667
>
>
>olaf
>-- 
>| Olaf Titz - comp.sc.student  |   o     | uknf@dkauni2.bitnet | old address |
>| univ. of karlsruhe - germany |  _>\ _  | s_titz@ira.uka.de   | is still    |
>| +49-721-60439                | (_)<(_) | praetorius@irc      | valid       |
>  "My heart is human - my blood is boiling - my brain IBM" - Mr. Roboto

Yea, but THIS client allows you to hack your login, and we wouldnt want
THAT now, would we?

Say NO to /away
Jeremy Nelson

-- 
jnelson@iastate.edu
Four
Lines
Suffice.
Newsgroups: alt.irc
From: ljz57640@uxa.cso.uiuc.edu (l.j.z. )
Subject: Re: Instructions on How to Self Kill
Organization: University of Illinois at Urbana
Date: Fri, 11 Dec 1992 22:02:06 GMT

a_murphy@Turing.ORG (Andrew A. Murphy) writes:

>In article <Bz0sqB.KBI@news.cso.uiuc.edu> ljz57640@uxa.cso.uiuc.edu (l.j.z. ) writes:
>>a_murphy@Turing.ORG (Andrew A. Murphy) writes:
>>
>>>### Notice -- KILL by rdragon for Beastie. (Instructions for self kill:
>>>1) request kill from irc op 2) if that fails instult oper 3) if that fails 
>>>flood an oper 4) if that fails mass flood all opers 5) if that fails you'll 
>>>just have to do it yourself.. 6) get oper status and do it yourself)
>>
>>>ok the unofficial, official list is now out...
>>>how to get yourself kill'd
>>
>>>1) request an irc op to kill you
>>
>>You forgot one:
>>
>>10) refuse to have net sex with an ircop 
>>
>>Happened to me once, and I was not amused.  
>>
>>--Juni
>>  one of the few remaining net sex virgins  :)
>>

>i'm sorry but you can't put 10 up that's abuse totally
>and a horrible reason to kill...
>would never kill for that reason
>*sighs*
>oh well some people do.. and kick for other reasons..

Andrew, honey, it was a *JOKE*.  I mean hey, you *did* say that this wasn't
to be taken too seriously, right?

>this subject is a total joke cause i kill all the time but won't kill
>without a good reason.. i just joke too much about it.

There, see?  You said it again.

Oh well, guess my sense o' humour is too warped for anyone to understand.
But hey, I *did* get kill'd once for not doing the net sex thing.  I
thought it was a really stupid reason, and deserved mention.    


:)


--L.

-- 
laura j zurawski         juniper@uiuc.edu        
"Sometimes you can't explain your actions...
	sometimes you can't explain yourself"   
"PUSH THE BUTTON, FRANK!"
Newsgroups: alt.irc
From: vince@world.std.com (Vince R Netz)
Subject: Irc client for the NeXT
Organization: The World Public Access UNIX, Brookline, MA
Date: Sun, 20 Dec 1992 01:24:04 GMT

Hmm, here I was happily getting my new NeXT box hooked up to the
internet, and am having trouble compiling the Unix version.
Stuff that went like a charm on my old Sun just don't work
right on this one.  Is there a specific client out there
for NeXT's?