NODE 9ca070ebGOPHER: misc
Karl Lui Barrus <klbarrus@owlnet.rice.edu>Sat, 18 Sep 93 23:31:41 PDT
Thanks for the feedback about links - I didn't read that far in the
server.doc! It looks like I could point to the EFF gopher for
legislation and stuff, if they wouldn't mind...?
But, stuff I link to has to be available from another gopher, right?
I mean, I just can't point to a directory on some machine and have
gopher retrieve the file for viewing? Or can I? Because I definitely
would like to have the RFC's and message digest stuff viewable, or
pointed to. Also, will gopher uncompress a file before displaying?
I think I should read the gopher FAQ :-) And look at WWW when I have
some time.
Also, where is the "Digital Silk Road" paper? I'd like to put the
text version in the "Digital Cash" section. I'd also like to put the
two reports at cwi up, but those are postscript...
gopher.wustl.edu has a TANTALIZING menu item for the ftp site, but I
got a connection refused message. I need to talk to Chael to see
exactly what kind of disk space we have to work with - it looks like
to me an ftp option retrieves files to the gopher site (chaos).
I put up some more stuff, including remailer public keys, but not much
more on anonymous mail and still nothing on clipper.
--
Karl L. Barrus: klbarrus@owlnet.rice.edu
keyID: 5AD633 hash: D1 59 9D 48 72 E9 19 D5 3D F3 93 7E 81 B5 CC 32
"One man's mnemonic is another man's cryptography"
- my compilers prof discussing file naming in public directories
NODE 9adf3dbeRe: GOPHER: misc
nate@VIS.ColoState.EDUSun, 19 Sep 93 06:39:45 PDT
Karl Lui Barrus coersed the electrons into symbolizing:
>I think I should read the gopher FAQ :-) And look at WWW when I have
>some time.
Speaking of WWW, I am working on a DoE project (the "Computational
Science Education Project", CSEP for short), and part of this prject
involves the development of a WWW-able book.... so what i am saying is
that I have quite a lot of experience with WWW, and would be more than
happy to help develop (or just plain develop) a set of HTML (the type
of document that WWW readers (such as NCSA Mosaic) read)... I don't
think that I would feel comfortable running it from the machines in my
laboratory, but I will speak to my boss about it when the time is right,
maybe I'll ask about letting people have their own home pages... that are
defined as being separate from the project or something.
Anyway, if anyone is willing to donate some drive space, and wants to
set up a WWW server, I know how, and I can get it done.
Just trying to do my part,
-nate sammons
--
+--------------------------------------------------------------------
| Nate Sammons email: nate@VIS.ColoState.Edu
| Colorado State University Computer Visualization Laboratory
| Finger nate@monet.VIS.ColoState.Edu for my PGP key
| #include <std.disclaimer>
| Always remember "Brazil"
+----------------------+
NODE 11c55985Re: GOPHER: dealing with postscript
strick -- henry strickland <strick@osc>Sun, 19 Sep 93 14:19:47 PDT
THUS SPAKE Karl Lui Barrus <klbarrus@owlnet.rice.edu>:
#
# Also, where is the "Digital Silk Road" paper? I'd like to put the
# text version in the "Digital Cash" section. I'd also like to put the
# two reports at cwi up, but those are postscript...
Suggestion: Put them under a gopher subdirectory named "Postscript
Files" inside the directory they are appropriate to. Then by default
people see the plaintext files and the "Postscript Files"
subdirectory. If people are postscript-capable, they can then go down
the next level.
Or append "(Postscript)" to the displayed file name, to make
it clear that way.
As MIME becomes integrated into internet tools and widely
available, this problem will solve itself. "application/postscript"
is already a standard MIME Content-Type.
In the meantime, don't shy away from making information available,
especially if it is in a format as "widely accessible" as postscript is.
strick