RE: Transfer confirmation "password" terminology is confusing

[Charles Daminato]

Well, we thought about that... but the only way to verify the auth_code for an incoming transfer is to actually TRY the transfer.   So, if we use the auth-code for the transfer password; the only option is to accept the transfer.  We needed to give them the ability to accept/cancel, so an extra step was needed.   Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chuck Hatcher Sent: February 5, 2002 8:57 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Transfer confirmation "password" terminology is confusing Why require both for .info and .biz?   If the auth info code is considered proof of ownership, why not let that take the place of the transfer password? ----- Original Message ----- From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 04, 2002 9:56 PM Subject: Re: Transfer confirmation "password" terminology is confusing In einer eMail vom 05.02.02 03:04:38 (MEZ) Mitteleurop�ische Zeit schreibt [EMAIL PROTECTED]: A while back, Chuck had mentioned that OpenSRS would perhaps try to change the wording of the transfer confirmation approval code from "password" to something else to avoid confusion: This will be difficult with info/biz If you f.ex. use 'transfer confimation code' users will be confused with 'authorisation code' (already probably most users are confused with 'authorisation code'. I would suggest something like 'Special transfer password' instead of another 'code' Matthias Eckert