|
Grex > Coop11 > #175: PicoSpan Documentation Fix - Scribble-family Commands | |
|
| Author |
Message |
i
|
|
PicoSpan Documentation Fix - Scribble-family Commands
| 
Jun 1 02:52 UTC 2000 |
As cfadm, i'm starting to look at "fixing" the documentation of the
scribble family of commands in PicoSpan so that what they really do
is spelled out better. (I don't have the rights, knowledge, etc. to
make any changes at all to BackTalk.) I'm entering this item to ask
for specific, sorta-technical feedback on this process. Please don't
drift off into policy debates, X-Files trival, Bush vs. Gore, etc. in
this item.
|
| 79 responses total. |
i
|
|
response 1 of 79:
|
Jun 1 02:58 UTC 2000 |
First Question: what PicoSpan (not BackTalk) commands do people know
of that give misleading or wrong information about what scribble, etc.
really do? (Purpose - i'm trying to find all the places where i need
to fix the wording.) I'm looking for responses along the lines of
"help foot-in-mouth at the PicoSpan Ok: prompt displays wrong info
about how the unsayit command works".
|
jep
|
|
response 2 of 79:
|
Jun 1 15:23 UTC 2000 |
The current "help scribble" command looks very good to me. (I am the one
who first brought up the point that keeping the /bbs/censored file
readable, but not telling anyone, is deceptive.) Here's the current
wording:
**** CENSOR ****
Censor -- mark a response "censored"
Form: censor N
or scribble N
Mark a response "censored". Unless "noforget" is
specified, it will not be shown. "scribble" will
also scribble over the text (hence expunging it),
but not before it copies it to the possibly publically
readable file "/usr/bbs/censored"!
THESE COMMANDS ARE A LAST RESORT MEASURE. ITS USE
IS STRONGLY NOT RECOMMENDED. DO NOT USE!!! (see
help etiquette, and it's probably too late anyway)
|
aruba
|
|
response 3 of 79:
|
Jun 1 15:57 UTC 2000 |
THe file name there is wrong - it should be /bbs/censored . (Also
"publicly" is spelled wrong and the first two sentences in capital letters
disagree on the number of commands.) I don't understand the last bit in
parentheses.
|
aruba
|
|
response 4 of 79:
|
Jun 1 16:01 UTC 2000 |
For some reason, "help expurgate" doesn't give any help at all. What's up
with that?
|
albaugh
|
|
response 5 of 79:
|
Jun 1 16:35 UTC 2000 |
I think something better than "don't use this command!" belongs there.
Explain when & why you'd want to use the command, and say that it should be
used sparingly, but not "DO NOT USE". Why have a command if you shouldn't
use it? You still need the "rm" command in UNIX.
|
janc
|
|
response 6 of 79:
|
Jun 2 05:36 UTC 2000 |
(Actually, Walter does have the access needed to edit Backtalk help
files or any other Backtalk scripts - they are all owned by cfadm. He
could probably even figure out how to do it. But if you have specific
ideas about what to do to Backtalk, I'll readily entertain them. I
don't think we have any emergency in progress here though, so I'm kind
of inclined to wait till we have a new policy before making a lot of
changes.)
|
mary
|
|
response 7 of 79:
|
Jun 2 12:25 UTC 2000 |
Is it possible, in PicoSpan and Backtalk, that when a person starts to
enter their very first item or response that they be given a warning that,
"Once text is entered in a conference there isn't a mechanism to again
remove it from public access. Think ahead and use care."?
The poster would see this warning only once. It would also put folks on
notice that should they choose to publish text here it will be published
for a very long time.
|
pfv
|
|
response 8 of 79:
|
Jun 2 13:18 UTC 2000 |
Reply? r
"WARNING! You are about enter a reply. Big Brother has decreed
that all postings on Grex are Grex property. You, as an author
have no say in deleting your own material, nor any sort of
ownership/authorship rights to your post. Grex will now hold your
hand and guard your crayon-work like the adult you are, and hopes
this has made you both more Thoughtful and Mature.
Have a Joy-Joy Day!
|
scott
|
|
response 9 of 79:
|
Jun 2 18:56 UTC 2000 |
Reply? r
"Warning! Despite the best efforts of a few people who don't trust
themselves or anybody else to think about what they are posting, things
here are pretty the same as they ever were."
|
krj
|
|
response 10 of 79:
|
Jun 3 04:31 UTC 2000 |
I think the warning should be given every time the user enters a response.
|