|
Grex > Coop8 > #49: Change the default to allow tels? | |
|
| Author |
Message |
| 25 new of 86 responses total. |
rcurl
|
|
response 50 of 86:
| 
Apr 13 07:30 UTC 1996 |
...but others besides staff like it too. Just give us total flexibility to
configure the system to our preferences, and we will all be happy.. 8^}
|
steve
|
|
response 51 of 86:
|
Apr 13 12:12 UTC 1996 |
Right.
Actually, I leave me perms on whenever possible, becuase a lot of
people seem to gravitate towards me, for whatever reason. I just don't
like tels. One of the reasons I've allowed them is that I've found
two Grex users who only knew of tel, and didn't know about write at
all! Knowledge transfer is an interestng thing to watch.
|
dang
|
|
response 52 of 86:
|
Apr 13 18:01 UTC 1996 |
Actually, I knew about write for mor than a year before I knew that tels
existed, and I still don't know how to use them because I've never used them.
My main mode of communication is bbs, and mail, which I maintain off site.
I don't, therefore, have an opinion on this, but I think, as a very related
topic, that we should put an item in the intro that talks about the various
real time commi
<sorry> communications programs, so people can know what tehy are and how to
use them. Personally, as a philosophical measure, I would like to see the
default as accepting all forms of communication, and tell people how to shut
them off.
|
rickyb
|
|
response 53 of 86:
|
Apr 13 19:18 UTC 1996 |
I think there was a problem with tels at m-net not too long ago. Someone
wrote a script which would tel everyone on-line and it told them to try it
for kicks. Seems it was a way to steal their passwords or something like
that. (I never run scripts of others).
Then there are the irritating ones from that small, but annoying group of
twits that seem to come and go every once and awhile. I certainly have not
seen those kinds of problems (or problem people) here at grex, I'm pleased
to say.
I support allowing tels as the default, but maybe the login screen (or, at
least newuser) could either explain to users, or point them to information
about how they can individually turn off their tels either per session, or
as their own personal default (ie; .login).
|
slynne
|
|
response 54 of 86:
|
Apr 13 20:51 UTC 1996 |
I also would support having "tel" as the default. I prefer tels to write.
I like to be able to do something else while the other person is typing.
In write, one must wait...and wait...and wait...for the person they are
talking to to type in what they are trying to say. When using tel, one
can do other things, like reading party or bbs while the person they are
talking to is typing. Heh, I have had some conversations with slow
typists where I was able to read whole items while they were typing their
responses to me.
I also would like to see a way to turn write off while still allowing
tels. I think I am just as bothered by write requests as steve and glenda
are about tels. ;) I, however, dont resent having to turn off something I
never wanted in the first place and in fact would be only too happy to
include another line in my .login.
|
dpc
|
|
response 55 of 86:
|
Apr 13 20:51 UTC 1996 |
I will continue to keep mesg n in my .login file since I don't like
"real-time" communications. I'm glad that mesg n stops tels as well
as writes!
|
ajax
|
|
response 56 of 86:
|
Apr 13 21:22 UTC 1996 |
For people who know how to use tel, but not write, as STeve
described, maybe the tel/write could be modified to tell a user
something like "steve isn't accepting tels right now, but he is
accepting writes. type !write steve to initiate a conversation."
|
scott
|
|
response 57 of 86:
|
Apr 13 21:28 UTC 1996 |
I think that I'm currently getting tels but not writes, courtesy of:
mesg -p t
|
scg
|
|
response 58 of 86:
|
Apr 13 23:01 UTC 1996 |
When somebody is accepting tels and not writes, or writes but not tels, it
will ask a user trying to do the thing they aren't accepting if they want to
do the other thing.
I find tels much less intrusive than writes. If somebody sends me an
irrellevant tel, I can generally just ignore it. Writes require me to drop
whatever I'm doing and respond to them.
|
slynne
|
|
response 59 of 86:
|
Apr 14 00:23 UTC 1996 |
Thanks, scott :)
|
rcurl
|
|
response 60 of 86:
|
Apr 14 06:23 UTC 1996 |
Scott, could you assemble a table of *all* the options for mesg (and what
they do)? A number have been scattered in different responses here, but
it would be useful to have them in one response - and maybe as a new item
in info.
|
scg
|
|
response 61 of 86:
|
Apr 14 09:16 UTC 1996 |
Try "!man mesg".
|
scott
|
|
response 62 of 86:
|
Apr 14 11:41 UTC 1996 |
What scg just said. I'm no guru; the best person to ask (if the man pages
disappoint) would be janc, the author.
|
rcurl
|
|
response 63 of 86:
|
Apr 14 20:10 UTC 1996 |
....5 screens later...say, how about assembling a *table* of the options that
doesn't make it a chore to find out about them, like the man pages do?
|
dang
|
|
response 64 of 86:
|
Apr 14 21:36 UTC 1996 |
Here you all go:
table of arguments for mesg command:
<none> report current status
n No meseges accepted, by write, chat, and tel
y Accept all messages from write, chat, and tel
p preferances
pa accept any messages. Default.
pw accept write (and chat, I assume) but not tel
pt accept tel, but not write and chat
m modes (affects write only, not tel)
ma accept both line and character bases. Default
ml accept only line (forces character to line)
mc accept only character (forces line to
character)
r recording of tels (huh command)
rn turns off huh command
ry turns on huh command
h helper flag
hn turns helper flag off
hy turns helper flag on
v report settings in verbose mode
|
ajax
|
|
response 65 of 86:
|
Apr 15 04:50 UTC 1996 |
5 screens later? The solution is clear, Rane: you need a taller
screen! :-) Thanks for the table Dan...it would be nice if that
were added to the mesg man page in a "SUMMARY" section.
|
rcurl
|
|
response 66 of 86:
|
Apr 15 15:59 UTC 1996 |
Put in a line saying to append these to mesg as -m, -ma, -v ....etc.
|
popcorn
|
|
response 67 of 86:
|
Apr 15 16:41 UTC 1996 |
Re way-back-there: STeve -- I think tels actually give the writer more of a
chance to compose their thoughts than writes do. With writes, I worry about
boring the reader, so I type as fast as my head can pump characters to my
fingers. With tels, I'll stop and backspace and rephrase until I have a much
more intelligible message.
|
popcorn
|
|
response 68 of 86:
|
Apr 15 16:43 UTC 1996 |
While we don't have total agreement, we do seem to have a majority in favor
of having more message types available by default.
I'm going to write a script people can use to change the mesg permissions in
their .login or .profile file (kinda like the script that people used to go
back to the old party options, but with more choices).
Then I'll change the default to allow writes, chats, and tels.
|
dang
|
|
response 69 of 86:
|
Apr 15 21:15 UTC 1996 |
r 66: Actually, it says that mesg will take themm with or without the '-' and
in any combination of some with and some without.
|
steve
|
|
response 70 of 86:
|
Apr 15 21:28 UTC 1996 |
(a)
(soft)
(whimper)
|
scott
|
|
response 71 of 86:
|
Apr 15 23:37 UTC 1996 |
(Hurrah!)
|
rcurl
|
|
response 72 of 86:
|
Apr 16 01:40 UTC 1996 |
So it does - after the reader has struggled to learn the rule as dash-flag,
it dashes the dashes. Just like a man......
|
janc
|
|
response 73 of 86:
|
Apr 16 13:40 UTC 1996 |
(Basically, the command syntax of "mesg" is a train wreck. Traditionally
only "mesg y" and "mesg n" did anything. As I added more options, I felt
the dash-flag syntax was more appropriate, but for consistancy I wanted to
retain the old syntax too. So I threw all caution to the wind and made it
merrily ignore all dashes and spaces, so you can put in as many or as few
as you like wherever you like.)
|
popcorn
|
|
response 74 of 86:
|
Apr 17 12:55 UTC 1996 |
(My .login file says:
mesg n -m c -r y -p a -h Y -v
)
(well, I think I took out the -v)
|