|
|
| Author |
Message |
| 25 new of 156 responses total. |
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.
|
aruba
|
|
response 36 of 156:
|
Jan 12 18:08 UTC 1999 |
Greg, would you type "only 21;only 31" at the next prompt and then answer the
(implicit) question in #31? Because I really don't get it.
|
steve
|
|
response 37 of 156:
|
Jan 13 15:35 UTC 1999 |
Grex was down for about 6 hours early Wednesday (4a - 10a) because
of a vandal.
|
gregb
|
|
response 38 of 156:
|
Jan 13 16:32 UTC 1999 |
Re. 36: Don't worry about it. It's pretty much a dead issue. I've decided
to take my concerns to one of the board members in the future.
|
remmers
|
|
response 39 of 156:
|
Jan 13 18:40 UTC 1999 |
The board doesn't regulate users' responses in the conferences.
|
jiffer
|
|
response 40 of 156:
|
Jan 13 18:52 UTC 1999 |
How will the board enforce people using 'Re. # XX'
Doesn't that go... oh, never mind.
|
krj
|
|
response 41 of 156:
|
Jan 13 19:37 UTC 1999 |
We will have a Code of Posting. The Board will appoint a Code Czar
who will review all responses before they are finally entered into BBS.
This may slow the conferences down a bit, but for tidyness, it's worth it.
:)
|
jiffer
|
|
response 42 of 156:
|
Jan 13 22:54 UTC 1999 |
ahh, but that would go against freedom
|
tpryan
|
|
response 43 of 156:
|
Jan 14 03:17 UTC 1999 |
BBSing takes a bit of skill. LIke keeping track of 99 conversations
(items) that you may pick up once a day or once a week. When I see a
response like:
re 77: Yep, that's how you do it.
And then I go back and do 'only 77', I find that the anticipation
outweighs the event, taking me time to read on something that I wasn't
following that close anyway.
|
bmoran
|
|
response 44 of 156:
|
Jan 14 04:49 UTC 1999 |
Was the vandal why I got a busy signal for most of the morning while
trying to log in?
|
steve
|
|
response 45 of 156:
|
Jan 14 04:51 UTC 1999 |
Nope. The phone gremlins got those. ;-)
|
bmoran
|
|
response 46 of 156:
|
Jan 14 14:38 UTC 1999 |
Ah, those pesky gremlins!You'd think -somebody- could write a quick
script...
|
gregb
|
|
response 47 of 156:
|
Jan 14 15:14 UTC 1999 |
Re. 45: Just don't call them after midnight. 8-)
|
aruba
|
|
response 48 of 156:
|
Jan 16 23:38 UTC 1999 |
I am getting ready to enter the last batch of items for the current version of
the auction; after that I plan not to accept any new items until summer. So
if you have anything you'd like to put in the auction, and haven't sent me
mail already, do so ASAP.
|
steve
|
|
response 49 of 156:
|
Jan 17 10:17 UTC 1999 |
I committed MOTDcide this morning.
This means I zapped the contents of the Message Of The Day
file, hence my oops message when you logged in.
Oops.
|
davel
|
|
response 50 of 156:
|
Jan 17 18:56 UTC 1999 |
You didn't have the contents in your scrollback buffer to past in?
|
steve
|
|
response 51 of 156:
|
Jan 17 19:59 UTC 1999 |
Yes, I have one but I'd been on for many hours and I exceeded it.
I did think of that.
|
kalki
|
|
response 52 of 156:
|
Jan 18 14:27 UTC 1999 |
|
rtg
|
|
response 53 of 156:
|
Jan 24 05:33 UTC 1999 |
If there's any serious effort to suggest this RE: # thing, could we at
least make it resp:# so it's clickable in backtalk?
|
devnull
|
|
response 54 of 156:
|
Jan 24 11:20 UTC 1999 |
Re #53: Nope. We should get the backtalk maintainers to change backtalk.
|
valerie
|
|
response 55 of 156:
|
Jan 25 04:51 UTC 1999 |
This response has been erased.
|
