7,475 karma · joined February 14, 2010
I hail from western Pennsylvania, work in San Francisco, and live in Oakland.
Email via: https://alanhogan.com/contact
My topcolor: ffb077
Twitter, GitHub: @alanhogan
That said, the concept of "Apple Sign-In" for Android and other platforms is an interesting one, not likely in the short term, but possible someday!
I appreciate the situation that the journalist found herself in, but if she wants her number to be a secret, she needs to make sure the people she calls know that, too.
I will file the information in this article as “good to know,” not “omg disaster”.
Here's what you aren’t seeing, if I may: Consumers see the end product. They intuit rules based on what they see. I only see pictures and videos sent to me, and then they are gone. From this their mental model becomes No one can see media that is not sent to them, and the media is gone after it has been seen. This is strikingly different from the way a developer at Snapchat models the world: We run a big warehouse full of data and media. We present this media to users based on logic that prevents arbitrary non-admin users from seeing others' content and from experiencing that content repeatedly. Oh, and we should eventually get around to writing that cronjob to delete old media. And once we rule the world, we can spend time playing with end-to-end encryption, maybe.
People aren’t stupid (mostly). They are just ignorant (in the literal sense). They are extrapolating in a way that makes sense in a physical world but not in the digital world.
The clearest analogy is that of actual dice vs. video gambling or the virtual spinner in a free-to-play game. With actual dice, what you see is what you get: fair odds. But that virtual wheel is 'weighted' to end on the worthless prize right after the jackpot space nearly every time.
https://alanhogan.com/buzz-is-already-dead (About the UI/UX nobody wanted)
https://www.nytimes.com/2010/02/13/technology/internet/13goo... (Failure to respect users and imagine any blowback from violating trust and privacy)
I will also add that I rarely report crime. This is somewhat learned helplessness as I do not expect any results. For example, calling Oakland's non-emergency number has resulted in me eventually giving up after getting nothing but a busy signal over and over. I was attacked by one of San Francisco's street addicts, but as I did not suffer any serious injuries, I did not waste my time reporting it. (I regret this on principle as surely that person has attacked others and will continue to do so.) I also do not report the obvious dealers hanging out on corners by our offices because I know from following the local (Tenderloin) police force's Twitter account that even if they make the arrest, the dealer will be released within weeks (possibly hours or days; not sure) back onto the streets. It is common for them to arrest the same dealers three times in two-month periods. (And no, they aren’t pot dealers; they are arrested with meth, crack, heroin, and other hard drugs ready for sale.)
(Notably, AutoPilot is not supposed to change lanes without explicit confirmation from the driver, which is clearly illustrated on the dashboard/panel.)
It's a stretch of road on which I have previously used AutoPilot many times.
I haven't confirmed this hunch as to the technique but it seems like a good compromise if there is a good reason to hide the password field initially. And I think there are some such good reasons. For example, if you are Google: Not everyone logs in to Google with a password. I have to log in to my work account using our company's SSO provider, so that Google account has no password. In this case, I shouldn't see a password field, as its presence will be more confusing than helpful. Still, a hidden-but-present password field would allow my password manager to work in the case that my Google account does in fact take a password. (Presumably care should be taken to avoid adding extra confusion to users of assistive technology.)