1. add an "avoid ambiguous characters" option (is that an "l" or a "1", an "O" or an "0", etc.).
2. encouraging people to type or generate passwords into/from random web sites is a bad idea -- perhaps even making the problem worse instead of solving it.
3. who's your target audience? The tech community already understands this. Is it my mother, the average user? She'd use this exactly once and then forget it. Why? "getvau.lt". While that's "cute" and us techies love crap like that, all Joe User knows is .com. When he tries to come back to the site tomorrow, he'll type in "getvault.com" or (more likely) "get vault" or "getvault", end up somewhere else, and never use your service again.
Comments
A couple of things:
1. add an "avoid ambiguous characters" option (is that an "l" or a "1", an "O" or an "0", etc.).
2. encouraging people to type or generate passwords into/from random web sites is a bad idea -- perhaps even making the problem worse instead of solving it.
3. who's your target audience? The tech community already understands this. Is it my mother, the average user? She'd use this exactly once and then forget it. Why? "getvau.lt". While that's "cute" and us techies love crap like that, all Joe User knows is .com. When he tries to come back to the site tomorrow, he'll type in "getvault.com" or (more likely) "get vault" or "getvault", end up somewhere else, and never use your service again.
HTH.