meta user
network profile
| bio | website | none.seriously |
|---|---|---|
| location | Germany | |
| age | 28 | |
| visits | member for | 1 year, 10 months |
| seen | 1 hour ago | |
| stats | profile views | 11 |
Physicist.
|
May 26 |
comment |
Why does the email subject appear before the body when composing an email? @uxzapper Good points! I guess we're looking for a compromise - forcing the writer to add a subject before the message is supposed to make sure (but often enough fails) that the reader doesn't have to read/skim whole paragraphs to learn that "Re: coffee" is actually about "Admin login on server 7 not working"; on the other hand the writer will also profit from it later on since they may end up in a "come on, I sent this to you last month, here I'll resend you the mail - was it "Re: cute little kitten" or "Re: Re: cute little kitten"?" discussion, also wasting everyone's time |
|
May 26 |
comment |
Why does the email subject appear before the body when composing an email? @LukeBornheimer That's actually even better, wish my bank did this; or at least ejecting the card while the money is prepared for release instead of afterwards, effectively wasting everyone's time... |
|
May 24 |
answered | Why does the email subject appear before the body when composing an email? |
|
Apr 18 |
comment |
Forcing users to use a particular pattern for passwords Any rule like "must contain at least one of !$ۤ$#" will most likely result in one of these symbols being appended (or prepended) to the usual password. In this example that's just 7-15 times more passwords, while adding an arbitrary character yields around 64 times more (not all 256 ASCII characters are valid, but nowadays you could use UTF-8 as well...). And unless you allow users to put a "Password reminder: '!'" somewhere they will either write it down or regularly reset the password... |
|
Apr 18 |
comment |
Forcing users to use a particular pattern for passwords @Izkata α? Remember, there's unicode nowadays... |
|
Apr 18 |
suggested | suggested edit on Forcing users to use a particular pattern for passwords |
|
Apr 4 |
comment |
What is the best way to request individual characters from a password? @user27478 That's what a two-factor authentication does, only usually in a way that is not limited to the finite amount character this "second password" has |
|
Apr 2 |
comment |
What is the best way to request individual characters from a password? @alexmuller I understand your UX aspect, but security first! Your question more concerns with "how to store" than with "is it a good idea" - How secure is asking for specific characters of passwords instead of the entire thing? is a better fit, especially with the accepted answer's quote "Contrary to popular belief, masked password, especially in e-banking sites, though they offer protection from basic keylogging, completely fail to other, more prevalent threats like malware utilizing social engineering.". => Use two-factor authentication |
|
Apr 2 |
comment |
What is the best way to request individual characters from a password? Don't. Ask at security.stackexchange.com why. (Basically what @Izkata said, but I bet one of the Thomases there will give you an awesome answer - the point is, noone but YOU should know your password, and if you forgot it it should be reset not retrieved) |
|
Mar 25 |
comment |
Language of language names in the language selector? I once had the joy of resetting an old Nokia 3210's language from an Arabic script to German. Nokia chose option 1 at that time. I had to use a second identical phone in parallel to even only find the language selection... So @Mike, I know what you mean |
|
Mar 25 |
comment |
Language of language names in the language selector? Remember: Automated translation should be optional |
|
Mar 19 |
comment |
Does leaving a field blank - mean “everyone” If you and your customer are discussion what a blank field can be interpreted as, how do you expect users to guess the meaning? Be explicit |
|
Mar 19 |
comment |
Does leaving a field blank - mean “everyone” Precisely: Explicit is better than implicit |
|
Mar 19 |
comment |
Does leaving a field blank - mean “everyone” @JoshuaBarron You're probably referring to the Zen of Python |
|
Mar 19 |
answered | Does leaving a field blank - mean “everyone” |
|
Mar 7 |
comment |
How do you give your user options without overloading them? It seems to totally lack the "Both files are actually identical, just wanted to let you know..." kind of message |
|
Jan 18 |
comment |
Computer login with password only, without username Hm, so in the end you'd still have entered two things, only in an ultimately more confusing way and with the additional risk that someone could "accidentally" place orders on your behalf (although that's of course just as likely as them obtaining your usual account data) |
|
Jan 17 |
comment |
Computer login with password only, without username So if you happened to receive something like "You cannot use that phrase" you could just try and use that phrase to pay at someone else's costs? |
|
Jan 16 |
comment |
Computer login with password only, without username Of course in that case the users had no choice of their PayPhrase but had to use a predefined (and by design unique) one, which would fix the biggest concern. However, the user would then have to write it down or store it somewhere due to the probably unrememberable-ness, and then you could just switch to SSL or token authentication directly... |
|
Jan 2 |
comment |
When should a year be added to a timestamp? @emory Sure thing, I don't blame anyone but those who decided in, say, 1990, that an upgrade could still wait :-7 But this question seems to be more about when to display the year which is hopefully stored anyway. Let's just say I stumbled upon more than one old site where the lack of posting year did increase the time required to validate the information provided. I don't expect this to happen to SE of course |
