You are not logged in. Login Now
 0-24   25-49   50-74   75-94       
 
Author Message
20 new of 94 responses total.
remmers
response 75 of 94: Mark Unseen   Jul 2 13:25 UTC 1996

Re #71: Thanks for the comments and suggestions, Jan.
arthurp
response 76 of 94: Mark Unseen   Jul 6 21:08 UTC 1996

Maybe it would be possible to have the .yeswrite and .nowrite store UIDs
instead of user names.  You'd have to run something on them to convert.  The
programming gets thick quickly.  :(
davel
response 77 of 94: Mark Unseen   Jul 7 20:02 UTC 1996

Sure it would be possible ... but it would be inconvenient for humans
attempting to maintain their own files to have to use UIDs.  Going by login
shouldn't really be any problem for the software, unless I'm missing something
really obvious.
janc
response 78 of 94: Mark Unseen   Jul 9 03:34 UTC 1996

login names would be much easier for the program to handle than uids.  Only
advantage of uids is that they don't get reused after an account is deleted
(yet).
arthurp
response 79 of 94: Mark Unseen   Jul 10 23:26 UTC 1996

If is used UIDs, then it could skip a lookup in /etc/passwd, no?  But making
it so that it *did8 the lookup when a UID was not found in the yeswrite file
would get into a fair amount of programming...
janc
response 80 of 94: Mark Unseen   Jul 11 19:27 UTC 1996

No, when you write someone, you give the login name, and it looks up the name
in the utmp file to figure out which tty that person is on.  Curretnly I don't
think write knows the uid of the person being written.  Of course, it knows
both uid and name of the writer, and that is the person that has to be looked
up in the recipeient's file.  You have to do a passwd file lookup on the
recipient anyway, because they .yeswrite file would be in his home directory.
Luckily, passwd file lookups are relatively fast with the password system used
on Grex.
mta
response 81 of 94: Mark Unseen   Aug 3 19:52 UTC 1996

No, it doesn't obviate the need for .yes/.no -- because that option still
means an interuption whenever someone wants to send a tel.  The .y/n files
mean that you can cf or e-mail blythly away without even a single interuption.
selena
response 82 of 94: Mark Unseen   Aug 4 05:10 UTC 1996

Sounds nice, doesn't it?
tsty
response 83 of 94: Mark Unseen   Aug 4 07:21 UTC 1996

so does   mesg n  ?
selena
response 84 of 94: Mark Unseen   Aug 4 14:52 UTC 1996

But, with mesg n, you can't be contacted by anyone! Why is it worse, to
allow some contact, than it is to totally cut yourself off, tsty?
You've never answered that.
davel
response 85 of 94: Mark Unseen   Aug 4 19:12 UTC 1996

He did too ... he said it's "discriminatory" and "anti-social".
selena
response 86 of 94: Mark Unseen   Aug 4 21:43 UTC 1996

And mesg n isn't?
mta
response 87 of 94: Mark Unseen   Aug 4 22:21 UTC 1996

mesg n is far more exclusive and anti-social than either .yes or .no since
it won't allow anyone in.  And I think anyone who thinks that people should
"just live with it" if they're being harrassed, or should just leave their
perms off, or should just pretend to be what they're not (ie male) so that
GREXers can pretend that harassment doesn't happen and that everyone is
egalitarian in their outlook is either a social ostrich or an MSP.


tsty
response 88 of 94: Mark Unseen   Aug 6 05:23 UTC 1996

there are two items in which i describe my position; briefly, i support
the .nowrite, selective filter and refuse to support .yeswrite since
it creates a "preferred population." i *ALSO* support, and *USE* and
*RECOMMEND* the   newmail  process  be running. 
  
imnsho, the *combination* of    mesg n   and   newmail   is infinitely
better than the "-ist" nature of .yeswrite.
  
tsty
response 89 of 94: Mark Unseen   Aug 6 05:31 UTC 1996

btw, mesg n creates *no* exclusivity that is prejudiced. newmail creates
*no* exclusivity that is prejudiced. .nowrite creates a prejudice that
is based from a specific individual's actions. .yeswrite creates a prejudice
that is based on nothing - no history - no contact - no knowledge - nothing.
pfv
response 90 of 94: Mark Unseen   Aug 6 06:31 UTC 1996

well, since there are assorted alternate ways for a "nonmember of
.yeswrite" to get in contact with another user, I still think the argument
is basically moot or specious.

I'm still rather puzzled on how you can refuse to help someone if they ask
for help.. And it seems your "function"..

With the exception of twits like "j0ker" and "niceguy", I try to help
anyone, anywhere and anytime - if I know the answer or can find it
"on-the-fly"..

Of course, you are free to _discourage_ the use of .yeswrite (.allow), but
in some cases I can certainly understand a desire to use it over the
.nowrite.
brighn
response 91 of 94: Mark Unseen   Aug 6 13:35 UTC 1996

Toasty, mail is prejudiced.  IT allows the user to determine who they wish
to respond to.  True, only .yeswrite allows a person to select a circle of
users, and *Everyone* else is persona non grata, but, if a person isn't going
to talk to anyone outside their circle of friends ANYWAY, why tease people
outside that group with the false promise of a !tel going through
(unanswered)?
popcorn
response 92 of 94: Mark Unseen   Aug 7 04:22 UTC 1996

("ouch!" says the dead horse)  :) :) :)
brighn
response 93 of 94: Mark Unseen   Aug 7 15:06 UTC 1996

Hey, Valerie, the horse needs to be plenty tender before you can make good
gelatin out of him.  =} =}
popcorn
response 94 of 94: Mark Unseen   Aug 7 22:32 UTC 1996

No thanks.  Gelatin isn't vegetarian.  :)
 0-24   25-49   50-74   75-94       
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss