You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-105      
 
Author Message
25 new of 105 responses total.
kentn
response 50 of 105: Mark Unseen   Jan 28 19:51 UTC 1995

I'd love to have the ability to block those repeated telemarketing-type
calls.  Some  caller ID boxes allow that (if you can afford them and the
caller ID service itself).  I also dislike repeated wrong number calls
from rude callers, many of those calls (I think) originating from the
same source (e.g., memory phones).  With caller ID I could call them
back after they've called me six times and made rude remarks, and ask them
to cease and desist.
scg
response 51 of 105: Mark Unseen   Jan 28 20:24 UTC 1995

That mail robot sounds like it would probably take a lot of time to write.
 Does anybody actually want to bother with that, considering the alternatives?
gregc
response 52 of 105: Mark Unseen   Jan 28 20:38 UTC 1995

Re #47: cicero
Ok, let's drop telemarketers out of this discussion for now, they only cloud
the issue. My point is that *anytime* you initiate a call, no matter it's 
purpose, you have, at the very least, *disturbed* someone else's privacy
and at most you have invaded their privacy.

As the disturber, you have responsibility of either making or not making
the call, as the disturbee, I then have the right to find out as much 
about you as possible. As the initiator of an action, you tend to waive
some of your rights when you start the interaction.

Unfortuneatly, our culture tends to train us from a young age with an
almost Pavlovian response to the phone. It rings, and most people drop
whatever they are doing and run to pick it up. It's a very strong urge
and it's hard to fight. Anytime that thing rings, your life is interupted
and you are unable to choose the moment of that interuption. That lack
of choice defines the invasion aspect in my mind. The caller, on the other
hand, always has a *choice*.
rcurl
response 53 of 105: Mark Unseen   Jan 28 22:37 UTC 1995

I have made a decision which I find that I am able to implement, and
that is, when I am on the pot, I do not run and pick up the phone.
andyv
response 54 of 105: Mark Unseen   Jan 29 03:34 UTC 1995

Folks, you can all move up here to Sault Ste. Marie where the telemarketers
know there are few people buying.  It is amazingly peaceful, but the standard
of living is hohum ;-)
cicero
response 55 of 105: Mark Unseen   Jan 29 07:48 UTC 1995

I thought there was a list that you could get on by calling the phone co.
the numbers of which telemarketers are not alowed to call.  Anyone else ever
heard of this?

I generally do have the above mentioned pavlovian response.  It really bugs me
to jus let the phone ring.  

As far as the initiator/receiver debate, I feel that it is a normal activity to
make phone calls.  It =may= disturb somone's privacy, but it does not
inheirently do so.  People receiving calls have a right not to pick up the
phone, but they do not have the right to necessarily know what my number is
just because I call them.

Not a popular view, but it's all mine!
ajax
response 56 of 105: Mark Unseen   Jan 29 08:42 UTC 1995

There's a direct marketing association you can write to, to reduce sales
calls and junk mail.  Anyway, to undrift for a moment....
 
I was thinking, another advantage of having officially sanctioned "anonymous"
accounts would be that they could allow new users to check out Grex before
deciding whether they want to go through the newuser program.  When folks
type "help" at the login:, it could mention you can log in as "guest" or
something for a quick look around.  If an official guest/anon account could
be configured to eliminate mail and password changes, and clear .cf files
and such, it would seem quite workable.  I've seen this idea used on many
MOOs and MUDs (multiplayer games on the internet) to cut down on once-used
accounts.  They sometimes use several guest logins, like guest1, guest2,
etc., so that when a user uses "guest" as a login, they're assigned a guest
account that's not currently in use by someone else.
 
<Ajax now cowers in expectation of the reaction of the Grex Establishment :)>
carson
response 57 of 105: Mark Unseen   Jan 29 11:13 UTC 1995

it's sounds like a doable idea in practice. I'm not sure how it'd
work out programming-wise, but udder dan dat, sounds, good.
srw
response 58 of 105: Mark Unseen   Jan 29 16:01 UTC 1995

This idea has been discussed before, but hasn't been addressed recently.
As I recall it is a tradeoff. The advantage of offering such an account
is that it would cut down on accounts created and immediately abandoned,
and that it would offer users a chance to see what conferencing was like
without having to spend the time required to create an account.
Those are big advantages.

The disadvantages are that we really would want "guest" to be a restricted-use
account. We would not want email or conference entries generated by "guest".
This would require changes to software, and in particular changes to picospan
for which we do not have access to the source code.

In the past, staff has always favored the current approach, but recently
the number of abandoned accounts has skyrocketed, and perhaps this needs
to be reevaluated. I'm sure I did not list all of the issues, though.
ajax
response 59 of 105: Mark Unseen   Jan 29 19:10 UTC 1995

I don't see the prob with guests making responses in picospan...that's the
issue that started this item.
rcurl
response 60 of 105: Mark Unseen   Jan 29 22:06 UTC 1995

Steve, haven't the abandoned accounts skyrocketed because we have not been
implementing an active reaping policy (and announcing same somewhere)? 

srw
response 61 of 105: Mark Unseen   Jan 30 04:19 UTC 1995

(1) Accounts get abandoned at whatever rate they do regardless of whether we
reap.

(2) We reaped accounts in early November, and will probably reap again some
time in early Feb. This would be on a three month schedule.
All accounts unused since early November will be removed.
The only thing standing in the way of this is a plan to identify and
mark selected accounts as invulnerable to reaping (commonly called "immortal").

This is a technical problem that will be talked about soon among the staff,
I'm sure.
cicero
response 62 of 105: Mark Unseen   Jan 30 07:16 UTC 1995

I agree with #59.  There's no problem with guest accounts posting to 
conferences.  We don't need to do a thing to Picospan.  The only technical 
question I can think of then is can we disalow sending of mail form said
"guest" account?  If so, then I think we should create these forthwith.
srw
response 63 of 105: Mark Unseen   Jan 30 07:52 UTC 1995

The main advantage of having a guest account would be to let new users
see what the conferences are like without having to run newuser.
Thus we would want to advertise the guest account at the login.
If we didn't suppress guest posts, my guess is that we would be flooded
with them, but I admit that I don't know how big a problem this would be.

Someone else will have to provide an estimate of the diffficulty of
suppressing mail and passwd from guest.

Here's a non-foolproof idea. Use lynx-shell for the guest account,
and we can write some special hypertext pages just for "guest".
We just leave off the pointers to stuff we don't want guest to use.

It only works for full-screen terminals, and is otherwise only parially baked.
ajax
response 64 of 105: Mark Unseen   Jan 30 10:30 UTC 1995

The main problem I see with guests sending mail is that they may expect
replies, which there's no guarantee *they*'ll get.  Though others express
concern over what other sysops might think if they get complaints about
mail from guest@cyberspace.org.  Granted it looks kinda bad, but (a) the
same messages can be sent by any made-up account here, and (b) so what? :)
So I'd say just alias "mail" to explain to the user that they should
really set up their own account to use mail; that there's no charge, nor
need for true identity.  If they want to work around the alias, so be it.
Guest mail could even be useful to mail staff that the sender's own Grex
account has a problem!  (Okay, I'm scraping for justifications here |->.
 
To deal with the password issue, and potentially have the login id "guest"
map to accounts for "guest1".."guestn", the login program could be modified,
the same way it recognizes "newuser" and "help" as a special commands, eh?
remmers
response 65 of 105: Mark Unseen   Jan 30 13:36 UTC 1995

{Even if we decided that Picospan posts from a "guest" account were okay,
we'd still have to do *something* to Picospan, as we'd want to disallow
shell escapes.
ajax
response 66 of 105: Mark Unseen   Jan 30 18:43 UTC 1995

Why?  Why not give guests the same service they can get by using a bogus name?
steve
response 67 of 105: Mark Unseen   Jan 30 22:32 UTC 1995

   A system where by people could "test" Grex sounds interesting, but
I'm afraid the system would be costly to users in that they'd have to
learn enough to do things and see what we're like, and then, if they
wanted to, they'd have to run newuser and learn a few different things.
   Thats not good, as far as I can see how it would go.
   What we really *really* need, is good documentation, less than
20 pages long, that people could finger and get for perusal.  Newuser
could mention it, and over time people would remember to finger
doc@cyberspace.org and get the help that would enable them to learn.
We really need a doc system that is more than the brochure, but not
a 200+ page manual so we can help folks out.
   The account reaping issue is that bad, but we do have to implement
it.  It isn't any harder to do 1000 accounts than 27, but in the past
we were able to ignore the issue for long periods of time since we
only got 9 newusers in any one day from July 20th 1991 to March 13th
1994.  It was after Valerie got the mention for Grex in a gopher that
the flood gates really did open up.  And of course, Marcus's work on
getting passwd, newuser and sendmail to use the shadow passwd database
system meant that effectively, it didn't really matter how many entries
we had in /etc/passwd.  But we will reap accounts soon, if only to
relieve the corpulance of /home.
remmers
response 68 of 105: Mark Unseen   Jan 31 11:16 UTC 1995

I've been conferencing for over 10 years on Unix/Picospan-based systems,
first on M-Net and now here.  The current discussion is at least the
half-dozenth go-around I've seen of the "can we set up a guest account
so folks can try things out?" question.  Despite all previous discussions,
it's never been done.  I suspect that's because of the effort that would
be involved in setting things up so that people can do enough to check
out the system but would not be able to do too much, and some skepticism
whether the benefits would be worth the effort.
ajax
response 69 of 105: Mark Unseen   Jan 31 22:26 UTC 1995

STeve, good docs would be nice, but don't negate benefits of guest accounts.
Most opposition so far is based on tech problems of preconceptions of what a
guest account "must" do: ban mail, ban responses or shells in picospan, or
require lots of time to set up.  What I'd propose is a pretty normal account:
add messages asking people to get their own accounts if they want to mail
or respond, but let them decide.  Other details: describe 'guest' in login's
help, bypass password in login, clear .cf files on login, ask term type on
login, and ask what menu or shell to start with.  Where is that experimental
spirit of Grex?  I fully admit this could turn into a nightmare, but how about
try it out and see?  And John, maybe it won't be implemented, but let's
decide *if* it should be first...lack of usenet didn't preclude making usenet
policy :).  Also, if a minimalist guest account like I described is desired,
it's pretty easy; I'd volunteer to set it up if I could get a copy of login.
steve
response 70 of 105: Mark Unseen   Feb 1 02:45 UTC 1995

   You wanna write up a functional specification for this?

   Far be it for me to say that we shouldn't experiment.  Perhaps
too many of us have been thinking about it for too long, and have
too many negative views of it.  So a FS might show some of us the
way to start it off.
   There is still the effort to do this that has to be found, but
perhaps someone will step forward during all this. It seems to be
worth thinking about more, at the very least.
popcorn
response 71 of 105: Mark Unseen   Feb 1 05:00 UTC 1995

Actually, you don't even need a copy of login to set this up.  You could
set guest's shell to csh or sh, and then from the .login or .profile file
ask what shell to run.
popcorn
response 72 of 105: Mark Unseen   Feb 1 05:00 UTC 1995

Incidentally, someone is already using the account name "guest", though
it doesn't look like this person has logged in since October 20.
remmers
response 73 of 105: Mark Unseen   Feb 1 11:55 UTC 1995

I think Rob is correct that you'd have to modify login to bypass
checking for a password.  Otherwise 'guest' could lock up the account
by changing the password.

A problem with relying on a .login or .profile is that 'guest' could
modify it and change the behavior of the account for the next person.
Regardless of what you'd want 'guest' to be able to do or not do, I'd
think you'd want to prevent 'guest' from modifying the environment of
the account for anything other than the current login.

Actually, if Rob has some enthusiasm for this and is willing to set it
up, fine.  I think the next step would be for him to work out the
details and present a plan.  In the meantime, I'll supress my
occasional inclination towards cynicism and see what he comes up with.
steve
response 74 of 105: Mark Unseen   Feb 1 14:25 UTC 1995

   If all the specialized programming that was needed for this was to
modify login for this, we're in good shape.  It would not be hard to
do that.
 0-24   25-49   50-74   75-99   100-105      
Response Not Possible: You are Not Logged In
 

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