Google| Subject | Re: Will Tony apologize? (was: Re: Colonial Photo & Hobby) |
| From | Tony Cooper |
| Date | 2014-04-25 16:28 (2014-04-25 10:28) |
| Message-ID | <plrkl9lv8ergvg49n6uipmt2i9m9t8139k@4ax.com> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Sandman |
| Followups | Sandman (15m) > Tony Cooper |
On 25 Apr 2014 06:13:18 GMT, Sandman <mr@sandman.net>wrote:
I did. The laptop mentioned below. It is not an example of a user who "sits down wanting to use a password" because that has nothing to do with what I said.Tony Cooper
I see what you've done. You've assumed, incorrectly, that my statement has to do with using a program that someone else has designed and I have no choice of what requirement there will be.There are many instances where using a password is optional and making the requirement of using one is a choice.Sandman
Please use an example instead of hot air, where the user sits down wanting to use a password.
Why are you ignoring very obvious aspect that the above is a situation where the requiring of a password to access the system is optional?Tony CooperSandman
My grandson's new laptop offered the choice. He could decide to require a password to access the system or decline to use a password. What is more of a choice of what "you want to do" than that?
He didn't want to use a password, he wanted added security. For added security, some sort of identification was a requirement, and password was (the only?) a choice. He didn't get a new laptop and said "Hey grandpa, I want to use a password! Do you want to join me using a password+ Let's go use passwords together!"
The "it's security, not a password" stuff is just a smokescreen. He has a choice. If he wants to have access protected, he can opt to have the system work only when a password is typed in. Or, he can opt for no such step. It's a clear example of a requirement being determined by what the person wants to do.
-- Tony Cooper - Orlando FL
2014-04-14-
