1password is such an overpriced waste. Just use truecrypt and textedit to keep your passwords. And copy and paste.
Encrypt volume, put file with passwords in volume, use it to log in
Save the hundreds of dollars Agile Bits is trying to screw you out of, and use free and open source tools.
I'm sorry you feel that way.
I think the simple explanation is that time is money and people with lots of passwords find value in not having to manually record and find a password for every login. 1Password does this for you and in the long run likely would save significant time over your manual method.
It's also a matter of personal preference and a real reason why we're free to use what works best for us. What works for you may not work for other people. That's why there are so many options for storing and saving passwords.
I would ask that you try to respect other people's opinions and decisions.
AGKyle, your support site appears to be down at the moment, so perhaps you can answer my question. Can 1Password deal with sites that ask for certain parts of the password only, like enter the 2nd, 5th, and 8th characters? Those things are hard enough with a simple password, with an auto-generated 20 character long random string, it gets silly.
We are not able to deal with those types of logins. At least not automatically.
These seem to be common outside of the US. So I haven't run into them personally. But a few suggestions for how to handle it.
1) Reduce the length of the password so that it is easier.
2) In the notes section of the application, enter something like this
1=a
2=3
3=Z
etc
This will allow you to easily see which letter is which.
If this becomes more common we may be able to work up a way to get this fixed. I'd suggest emailing the site and asking them for an alternative method to login though. This seems like a lot of hassle for little gain. Anyone that actually has your password can simply count. Or at least, I'd hope they could count.
3) Use a password you can easily type.
No one says you have to use a 20 character long generated password. We realize that in a lot of cases users need to be able to type in their password or it needs to be memorable enough to do so. In this case there's no harm in deviating from that idea. Just don't re-use the same password and you'll be better off for it.
I hope this helps. And i'm really sorry about our support site being down. We use TenderApp.com and they've been having some real trouble the past 4 days or so. We're just as unhappy as our users are about this.
Alternatively you can also email our support system.
support (at) agilebits.com