Hi - i see that you guys just added a captcha to your login. This is a problem because we wanted to automatically check the status of our domains with a script. I talked to your customer service department and you guys said that was OK.
However, now that you are requiring the code to login, this becomes impossible. Is there a way around this using the API or the API Key?
captcha will mess with my automatic login filler called 1Password. I don't want to have to type! I just want to press one button and have it log me in to everything, PayPal, Dynadot, and all my favorite forums!
Your captcha will make me do additional typing =/ Not fun.
This is also a pain for me, I get a captcha from one location but not from another.
I also was told by support staff that is would be fine to script checks.
What is with this?
Do you really want us writing code to get around captcha's to keep us as customers when your API is still not mature enough to do what we want and only offered to a limited audience.
When given permission for this it is annoying...
How about offering a alt-login page where we can generate and assign a login hash that only we know?
In addition it is incredibly annoying to have to type in a code each time we login.
Having it does not prove security either, as I can login from another ip, and then pass the cookie to the other ip's server and it thinks I am logged in.... you verify ips for captcha but not for sessions.... shame shame shame, just trying to make it harder for us honest people who like to simplify things for themselves.
..... and now they are gone...
[This post has been edited by h_atlanta_us on Feb 13, 2008 5:03pm.]
Having an API key will allow you to search for and register domains. You wouldn't be able to check the status of the domains in your account. If the captcha appears in the sign in box, then the captcha numbers must be entered to sign in.