Hey, @united social media person: I know this isn't your fault. But the entire computer security community thinks this password policy is exactly backwards and is putting your customers at risk. Seriously, this is just about unanimous. Tell your boss to get this fixed.https://twitter.com/united/status/960423339423449088 …
-
-
Replying to @mattblaze @united
The browser/pw-mgr folks need to get with the program too and implement auto-fill as fake keystrokes not paste so incompetent policies like this can't be implemented.
2 replies 1 retweet 17 likes -
Replying to @RichFelker @mattblaze
Why couldn’t browser makers just disallow the disabling of paste as an entry method? Would fix this for everyone at once. Is there any scenario where disabling paste actually makes sense?
4 replies 0 retweets 7 likes -
While its plausible ( but not advisable) to not allow paste in username/password fields, killing paste entirely is a really, really bad idea... Do you never write text lol ally, spell check etc and then copy/paste into a browser field?
2 replies 0 retweets 0 likes -
Anywhere you can type, you should be able to paste, and I’m not entirely convinced that the web page has any business knowing that you pasted instead of typed.
1 reply 0 retweets 2 likes -
Consider pasting source code containing newlines and tabs. You don't want the page to interpret the tab character as "move to next form field".
1 reply 0 retweets 0 likes
Ideal solution is probably: send fake keys if entire text to paste is printable characters, paste event if it contains newlines/tabs/anything else.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.