I'll see what we can do (to change a system we've been using for a long time *heh*)
Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Robert L Mathews > Sent: October 18, 2001 12:48 PM > To: [EMAIL PROTECTED] > Subject: Re: Transfer confirmation "password" terminology is confusing > > > At 10/18/01 7:22 AM, Michael J. Masin wrote: > > >>Wouldn't it be even more convenient to provide all this in a > pre-configured > >>link so that the client just needs to click it instead of clicking and > >>typing/pasting two words in two input fields? > > > >Amen! So many try to key in the information rather than cut/paste (and > >never get it right.) > > Which brings me to another nit-pick: a lot of people don't understand > case-sensitivity. This could be fixed by using numbers only as the > approval key, rather than strings of letters like "dhYaDSmM". When > generating initial default passwords, etc., I like to use numbers-only > with even 1 and 0 removed (to prevent confusion with "L" and "o"). > > An eight-digit numbers-only string using digits 2-9 still gives you 16.7 > million possible codes, and it's impossible for a user to misinterpret or > mistype. (OK, I guess they could have Num Lock off, but at least they'll > probably figure it out, whereas people who don't understand > case-sensitivity won't.) > > But Kai Schaetzl's suggestion (a short URL eliminating the need to retype > the key entirely) would be even better than all this. It could just take > you to a page that has "Approve" and "Deny" buttons (as well as the WHOIS > comparator, etc.). It couldn't be that hard to set up a system to deal > with URLs like: > > http://approve.opensrs.org/4578664432783784 > > And that eliminates all of these problems completely. > > -- > Robert L Mathews, Tiger Technologies > > Put an animated US flag on your Windows desktop: http://deskflag.com/ >
