I have read the prior replies and looked at the recommended links with
interest and have learned a lot - thanks, all!
I would like to suggest that a user could select a relatively strong
password and write down something close to the password. They would
then need to remember only what the
eBay's Selling form analyzes user behavior to progressively display
features/functionality on the form (so a beginner will see a
simplified version, and as they gain experience using the form they
will see more and more features). And they also let you customize the
form (add/remove features) at
That great Liz, saved me a job.
I've always been a bit bemused why the Async tools are so expensive.
I looked at UserZoom but couldn't justify passing on the costs to
some of my smaller (yet worthy) clients so I ended up building my
own.
Hoping that Loop11 is *affordably priced*.
. . . .
[disclaimer: I've worked for TiVo as a security/privacy engineer for ~8
years, am currently on leave to finish my MS Design. I can answer
questions about the general work environment, but don't know details
about this particular opening other than what is in the listing. --jet]
I really enjoyed this. It most made me think about privacy. Although
mobile technologies do not necessarily afford privacy, you're at least
dealing with a small screen that you can be discrete with. The
projection of information within shared spaces certainly adds
'texture' for people to base
I really don't think that's a good idea. I've never tested it, but my
gut says that:
1) if you use it so seldom you don't remember it, then you use it so
seldom you don't remember the modification (which of those variations
you proposed did I use? I should write it down)
2) if you use
Lost in this discussion of password strength is, how do we handle
multiple failed logins, forgotten passwords, and compromised passwords?
If your overall design (is this where we get into service design?) is
put together correctly, a compromised password (or an attack on an
account) isn't
Sounds like encryption http://en.wikipedia.org/wiki/Password_cracking to
me like wep http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy on my
wireless network at home.
The systems in place have trained the way I choose passwords. I have a
standardized way. I can recall 4 systems at the moment,
There are also two flavors of Deletion: true delete and move to
trash (from which the user can retrieve it later). A third flavor as
well, for some products: Hide. Remove from library (other other view)
but don't do anything with the file on disk. (And I think Adobe Bride
has a flag
I support Dev in suggesting the ellipsis ... to differentiate
related controls where the difference is that one acts immediately
and the other requires confirmation. A confirmation of a delete is
technically a dialog box, although a lightweight one, and the
ellipses is a convention here. Delete
2009/4/16 Erik Wingren i...@interactivism.com:
1. What is your thinking/point-of-view on application-level security
requirements for a mobile app, where one of its' features is to store
personal, potentially sensitive data, when the app runs on a mobile device
that already has built-in
Hi all
I was wondering if anyone is planning to attend MEX 2009, London this year.
I had registered a seat on the website but currently am unable to go for the
event due to client work. The terms conditions of the conference require
me to pay atleast 50% of the conference fee for my
12 matches
Mail list logo
