Twitter | Search | |
This is the legacy version of twitter.com. We will be shutting it down on 15 December 2020. Please switch to a supported browser or device. You can see a list of supported browsers in our Help Center.
Ryan Feeley
Coming soon to Firefox. We’ll let you know when you go to type your password into an insecure (HTTP) page or form.
Reply Retweet Like More
Rebecca Murphey 23 Nov 16
Replying to @ryanfeeley
love the idea but for average user, what do “insecure” and “compromised” mean? suggest plainer language.
Reply Retweet Like
Ryan Feeley 23 Nov 16
Replying to @rmurphey
Though users act differently during tests with passwords, we're going to test the language with them and once it's in Nightly.
Reply Retweet Like
Giving Thanks for Wearing Masks 23 Nov 16
Replying to @ryanfeeley @mikeal
Can't help feeling "compromised" is too tech audience oriented. Everyone knows "hacked."
Reply Retweet Like
Ryan Feeley 23 Nov 16
Replying to @mileselam @mikeal
Though users act oddly during tests with passwords, we're going to test the language with them and once it's in Nightly.
Reply Retweet Like
Derek Nutile 25 Nov 16
Replying to @ryanfeeley
Could you provide a URL for the specs on this?
Reply Retweet Like
Ryan Feeley 25 Nov 16
Replying to @dereknutile
Not for the faint of heart, but here's the bug tree:
Reply Retweet Like
http 26 Nov 16
Replying to @ryanfeeley @willstraf
Nice progress! But "could be compromised"? Better use "are sent to public" or something.
Reply Retweet Like
Ryan Feeley 26 Nov 16
Replying to @SwissHttp @willstraf
We'll test the copy with users now that it's in Nightly. "Intercepted" might be better.
Reply Retweet Like
Kirils Solovjovs 26 Nov 16
Replying to @ryanfeeley
That's not a password field though.
Reply Retweet Like
Ryan Feeley 26 Nov 16
Replying to @KirilsSolovjovs
Good eye! It appears on password fields, and username fields (which are harder to detect, as there is no username type)
Reply Retweet Like