|
|
| Author |
Message |
| 25 new of 156 responses total. |
senna
|
|
response 11 of 156:
| 
Jan 5 13:51 UTC 1999 |
Request to all: Please don't paste inane repetitive messages like spam
all over agora.
|
senna
|
|
response 12 of 156:
|
Jan 5 13:52 UTC 1999 |
Woohoo, boy. I think sarcasm is dripping all over my keyboard, it'll
take forever to clean up. Sorry :)
|
rcurl
|
|
response 13 of 156:
|
Jan 5 18:15 UTC 1999 |
You might want to post that in all the conferences......
|
gregb
|
|
response 14 of 156:
|
Jan 6 15:00 UTC 1999 |
Re. 11: Since not everyone reads all the confs., it seemed logical to post
it this way. If there's an alternative that accomplishes the same goal, I'd
like to know.
|
toking
|
|
response 15 of 156:
|
Jan 6 16:34 UTC 1999 |
sure there is...walk up to everyone you see and pee on their
shoe...it'll be just about as annoying
|
albaugh
|
|
response 16 of 156:
|
Jan 6 16:58 UTC 1999 |
No, create an item announcing the "refer to response item # please" request,
then link that item to every other conference! :-)
|
aruba
|
|
response 17 of 156:
|
Jan 6 17:00 UTC 1999 |
Honestly, Greg, I don't really understand what response 10 means, becasue I
don't know what you mean by "message number" - do you mean for people to
refer to the response # they are replying to (so I should have said "Re #14"
at the beginning of this), or do you mean I should put the item number (in
this case, 3) in each response?
|
gregb
|
|
response 18 of 156:
|
Jan 6 17:17 UTC 1999 |
Re. 17: Response #. Sorry for the confusion.
|
rcurl
|
|
response 19 of 156:
|
Jan 6 17:29 UTC 1999 |
It might have been better if this idea had been posted not as an
identical (somewhat unclear) response in many conference, but as
a specific comment in a conference about a particular response (which
had not identified the response to which it was responding). After
all, many responders do Re# in their responses.
|
senna
|
|
response 20 of 156:
|
Jan 6 20:06 UTC 1999 |
It might have been better just to use the "only" command to figure out what
messages they were referring to. Occasionally I miss the message someone's
referring to. I either ignore it or I scroll back and find out what they're
talking about or I use my deductive skills to get into the line of
conversation.
|
aruba
|
|
response 21 of 156:
|
Jan 7 02:01 UTC 1999 |
Yeah, if in my judgement what someone is saying is worth reading, it's usually
worth figuring out what they're talking about. For instance, in item 2 of
Agora I saw this response:
#87 of 92: by Greg (gregb) on Tue, Jan 5, 1999 (23:51):
I heard Leonard Nimoy read the whole thing on one of his albums some
years ago. The album (whose name escapes me) called it something
else. I had thought it was his LN's work.
And frankly, was quite confused about what gregb was talking about. Since
things about Leonard Nimoy tend to interest me I scrolled back about 5
responses and found a reference to the Desiderata, and guessed that that was
what "the whole thing" was referring to.
|
gregb
|
|
response 22 of 156:
|
Jan 8 14:37 UTC 1999 |
Re. 20, 21: "scrolling back" isn't as easy as you make it sound in Picospan,
unless there's a command I don't know about. And why put more work on the
reader when it's much simpler if the author simply puts a msg. ref. in their
msg. As for the Nimoy ref.: You'll notice that I included a source ref. at
the beginning, which eliminates any confusion.
|
senna
|
|
response 23 of 156:
|
Jan 8 15:09 UTC 1999 |
Oh, right, hadn't noticed that part, oh great behavioral manager of agora.
|
scott
|
|
response 24 of 156:
|
Jan 8 15:11 UTC 1999 |
Re 22: Most people who telnet or dial in can scroll back in their terminal
program. PicoSpan lets you enter a responce number at the "Respond or Pass"
prompt, or you can try a negative number for the number of responses from the
end to display.
|
aruba
|
|
response 25 of 156:
|
Jan 8 15:40 UTC 1999 |
Re #22: Huh? What source reference? As I said, I had to work to figure out
what you were talking about. (Not that that bothers me.)
|
remmers
|
|
response 26 of 156:
|
Jan 8 17:36 UTC 1999 |
Re 2 responses back: Right. For example, entering "-5" at the "Respond
or Pass" shows you the last 5 responses.
|
mic
|
|
response 27 of 156:
|
Jan 8 22:01 UTC 1999 |
Whilst PicoSpan supports such retrieval functionality of messages, I agree
with Greg. It is more considerate and helpful to note a reference number.
That way you can scrollback through your terminal software, or retrieve the
referenced message by typing the reference number at the prompt.
|
valerie
|
|
response 28 of 156:
|
Jan 10 00:29 UTC 1999 |
This response has been erased.
|
davel
|
|
response 29 of 156:
|
Jan 11 11:44 UTC 1999 |
Hey, that sounds interesting.
|
gregb
|
|
response 30 of 156:
|
Jan 11 14:34 UTC 1999 |
Re. 24: Your assuming, of course, that everybody's coming in using a PC.
At work, I'm using a dumb terminal, so I don't have scrollback. Moral: Never
assume a user's capabilities.
Re. 25: Same place you put yours.
Re. 26: Thanks, mic
Re. 28: 6'1". What's your theory?
|
aruba
|
|
response 31 of 156:
|
Jan 11 14:49 UTC 1999 |
Well, you lost me. If the response I quoted in #21 is OK with you, I really
don't understand what you're objecting to, Greg.
|
keesan
|
|
response 32 of 156:
|
Jan 11 17:00 UTC 1999 |
I find the referring to response numbers rather confusing, and would prefer
more context to the most recent responses. It is difficult to keep all four
comments and all four numbers in my head and then go back and look at the four
previous responses and try to remember evertying at once.
|
remmers
|
|
response 33 of 156:
|
Jan 11 18:07 UTC 1999 |
Re resp:30 re resp:24 - No, Scott isn't assuming that "everybody's
coming in using a PC." He explicitly said *most* people who telnet in
have scrollback capability, not everybody. I imagine that's true. And
as Scott also pointed out, you can always use Picospan's internal
"scrollback" capability (by entering a negative number at the "Respond
or pass"), even on a dumb terminal.
|
mdw
|
|
response 34 of 156:
|
Jan 12 06:19 UTC 1999 |
If I'm on a dumb terminal, I find it handy to have a bit of scratch
paper to write down notes like response #'s & the like. If I have X, of
course, I can usually get by with another xterm window or the like
(sometimes I'll even type stuff out at the command line even though it's
not even vaguelly a real command.)
|
gregb
|
|
response 35 of 156:
|
Jan 12 15:28 UTC 1999 |
Re. 32: Keesan makes an interesting point. If your reading a series of
msgs. in Picospan, and you dont't have scrollback capabilities, it can be hard
to remember what msg. # your referring to, which makes mdw's suggestion of
using scratch paper the best course of action. If your using Backtalk it's
a little easier.
|
