1993-11-12 - HARDWARE MAILING LIST ON-LINE

Header Data

From: jdblair@nextsrv.cas.muohio.EDU
To: cypherpunks@toad.com
Message Hash: 1f8e2a0a4f9b7149f2adf5b34013fb62a6ab275fdf555a2da9fdda6cb8c8af38
Message ID: <9311121924.AA17669@ nextsrv.cas.muohio.EDU >
Reply To: N/A
UTC Datetime: 1993-11-12 19:05:07 UTC
Raw Date: Fri, 12 Nov 93 11:05:07 PST

Raw message

From: jdblair@nextsrv.cas.muohio.EDU
Date: Fri, 12 Nov 93 11:05:07 PST
To: cypherpunks@toad.com
Subject: HARDWARE MAILING LIST ON-LINE
Message-ID: <9311121924.AA17669@ nextsrv.cas.muohio.EDU >
MIME-Version: 1.0
Content-Type: text/plain


The hardware off-shoot of this list is finally on-line!

You can subscribe to the list by sending a subscribe request of the form:
SUBSCRIBE cp-hardware <name>
to listproc@nextsrv.cas.muohio.edu

I have decided to call the list 'cp-hardware'.  While perhaps this is
somewhat more boreing of a name than punk-net, or the like, it is more
descriptive of the list as a whole.  Thanks to all of the people who sent
me mail requesting to be on the list- your're requests are why I've set
the list up.  However, I decided it will be simpler for people who are
interested to send the subscribe request themselves.  This should
eliminate, or rather minimize errors.  So, if you sent me a request
previously, you still need to send a request listproc.

The intention is that the list will be a forum for discussion of hardware
issues related to computer privacy, as well as dicussion, design, and
hopefully construction of several projects.  If the list gets going
sufficiently well, I'll set up an anonymous ftp site for the storage of
archive, schematics, and anything else that is related.

When you subscribe, you will get a welcome message which describes what I
see the list could be.  Your feedback is appreciated.  A short (very
short) informational file can be requested by mailing

INFO cp-hardware

To listproc@nextsrv.cas.muohio.edu, although the welcome message is I
think more descriptive of the list at this point.

so, punks, why stop at writing code?  Let's build hardware!
-john





Thread