From pycyn@aol.com Tue Nov 27 08:28:48 2001 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_0_0_1); 27 Nov 2001 16:28:49 -0000 Received: (qmail 41140 invoked from network); 27 Nov 2001 16:28:48 -0000 Received: from unknown (216.115.97.172) by m5.grp.snv.yahoo.com with QMQP; 27 Nov 2001 16:28:48 -0000 Received: from unknown (HELO imo-d06.mx.aol.com) (205.188.157.38) by mta2.grp.snv.yahoo.com with SMTP; 27 Nov 2001 16:28:48 -0000 Received: from Pycyn@aol.com by imo-d06.mx.aol.com (mail_out_v31_r1.9.) id r.4b.14def930 (4230) for ; Tue, 27 Nov 2001 11:28:44 -0500 (EST) Message-ID: <4b.14def930.2935193c@aol.com> Date: Tue, 27 Nov 2001 11:28:44 EST Subject: Re: [lojban] The end of the wiki To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_4b.14def930.2935193c_boundary" X-Mailer: AOL 6.0 for Windows US sub 10535 From: pycyn@aol.com X-Yahoo-Profile: kaliputra --part1_4b.14def930.2935193c_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 11/27/2001 8:57:03 AM Central Standard Time, jay.kominek@colorado.edu writes: > His other contributions consist of exclaiming how broken Lojban is, and > making up some wild solution. And where he at least has you remotely > interested (redoing the gismu), he doesn't bother to describe how he might > redo them, (most likely because that topic met with a modicum of > acceptance, which isn't any fun) but we're now being subjected to his > variant of the alphabet, which is _not_ related to Lojban. > Well, it seems as related as various fairy futharks have been (and has the advantage that things don't all look the same). The complaints without details are a greater problem, however, the more so since attempts to get the missing details are met with a runaround: repetition, "it's obvious," "why do you think it's OK" and the like. And what does emerge often turns out to be irrelevant (back to the issue of whether he has a clue what Lojban is about). Thinkit maybe a troll, or he may simply be inarticulate or not a very clear thinker (I have worried about his name). But, hexadecimalism aside, he has only consistently been what most of us have been sporadically and, as with us, even some of his flights have had enough meat to provide useful comments and discussion (though not quite worth the fuss, I judge). Let him hang around -- we can do our own censoring if he gets to bad:"Oh, thinkit again; I'll just skip that one." --part1_4b.14def930.2935193c_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 11/27/2001 8:57:03 AM Central Standard Time, jay.kominek@colorado.edu writes:


His other contributions consist of exclaiming how broken Lojban is, and
making up some wild solution. And where he at least has you remotely
interested (redoing the gismu), he doesn't bother to describe how he might
redo them, (most likely because that topic met with a modicum of
acceptance, which isn't any fun) but we're now being subjected to his
variant of the alphabet, which is _not_ related to Lojban.


Well, it seems as related as various fairy futharks have been (and has the advantage that things don't all look the same).  
The complaints without details are a greater problem, however, the more so since attempts to get the missing details are met with a runaround: repetition, "it's obvious," "why do you think it's OK" and the like.  And what does emerge often turns out to be irrelevant (back to the issue of whether he has a clue what Lojban is about).
Thinkit maybe a troll,  or he may simply be inarticulate or not a very clear thinker (I have worried about his name). But, hexadecimalism aside, he has only consistently been what most of us have been sporadically and, as with us, even some of his flights have had enough meat to provide useful comments and discussion (though not quite worth the fuss, I judge).
Let him hang around -- we can do our own censoring if he gets to bad:"Oh, thinkit again; I'll just skip that one."   
--part1_4b.14def930.2935193c_boundary--