After over a week sitting on MD with no apparent response, I thought I would 
bring this message to the (temporarily) ailing MF list.  

I think the symptom of no response on MD is due to information overload,
which would prove the point I raise in this message.  

By moving this to MF, I hope to at least have a few eyes look at the idea to
see if it has any Quality, since the lack of response on MD can't be taken to
mean anything for sure.

If anyone would like to explore this project and/or would like to help implement
it, former people who have administered a BBS would be helpful, or systems 
administrators.  

If this were erected, the BBS/Community could have a distinctive face to it
(like fix.no), so Qualicists experienced in C/C++ (or even Java) would find 
the scripting language "bz" easy to express in.  The interface for this 
hypothetical BBS (and all commands) could have a distinctive MoQ / Pirsig 
theme to them, and conferences could be built for many subject areas,
such as philosophy, economics, Lila, ZMM, technology, general discussion,
relationships, etc. etc.  I think this would ensure a flourishing MoQ
community. 

(ALSO, I do recommend current Qualicists type their name in quotes at 
Google.com.  You will find your MoQ thoughts sometimes drowning out 
important information about you. Some may like this, but I don't.  The BBS
would ensure a nice isolated pool on the internet safe from crawling spiders.)

--s

 
----- Forwarded message from Joel Kotarski <[EMAIL PROTECTED]> -----

I buried this in an off-topic to make a point, but I'll repost it in a separate 
message here:

"I'd like to make a suggestion:  MoQ.org might consider voting on 
        an electronic community in the form of an older style Bulletin Board Service.
        This provides the low-tech atmosphere that allows for a great mixture of
        dynamic and static discussions and live interaction between members.
For a great example of such a community, try this:
        telnet://fix.no

This solution would resolve a number of problems that are arising as the MoQ.org 
        community grows.  I'll be happy to help implement if asked.."

I can see that Dynamic Quality is calling for the next evolution of the MoQ.org 
interface,
mainly probably because of the stream of intelligent contributors has increased the 
flow
of information.  

We are suffering from information overload.

I must say that I have enjoyed _immensely_ much of the content that drifts into my 
mailbox 
from MoQ.org in both the MD and MF lists.  Nonetheless, I can honestly say that I have 
only
been able to read about 1% of the whole.

A good static pool, a place to visit, is needed.. I believe.   This will allow for 
an _active discussion_ and _dialogue_ to develop between members of the community, now
separated from each other.

If the administrators of MoQ.org would like to consider a Bulletin Board setting, 
here is a free solution.. Look into BBBS, a free bulletin board service that can be 
installed on
the box that runs the moq.org website.
         http://linux.davecentral.com/articles/view/701/

If anyone wants to test this type of interface beforehand, login to the fix.no service
and see how this feels.  (If you are having trouble connecting, please see 
http://www.fix.no/login/
)

Imagine that anytime you want to discuss MoQ, you could LOGIN to the community.
The information would not have to be downloaded in mass to your mailbox, but would be
stored on the BBS, and could be viewed instantaneously.  The threads will be managed
better.. Searching functions will be better.  
Imagine that you could talk about a probing MoQ question in the middle of the night
with someone who also might wish to discuss it live, speaking in a natural 
conversational
way, in sentences rather than books.  Imagine being able to setup meeting times to 
discuss
special topics.  The dynamic flow of information then isn't compulsory, but voluntary.

This is a major architectural change.. and might not be the best alternative,

but 

EVOLUTION IS NEEDED..

--s


MOQ.org - http://www.moq.org

Reply via email to