And neither should exist. Asynchronously asking for a password is an absolute no-no.https://twitter.com/KrauseFx/status/917736145353695232 …
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I think your model has users accessing web apps via links from other sites, which falls under "prompted for pw".
Should never be accessed except via bookmark or manually typed site name.
So you are saying emails shouldn't have links, basically?
I'm saying login via a link (not just from email, from anywhere) should not be encouraged or even permitted.
Hard stance. I suspect many, many businesses would have to change significantly for that. And it wouldn't work till everyone (or the vast majority at least) did it anyway
Furthermore as a user it sounds like a nightmare. If I want to go straight to an interior page after a session is over I would no longer be able to, and would instead need to login via Doman or bookmark then go to interior page
Idea of "after a session is over" is bogus. Login should be permanent for device/browsing context.
Then there's not even any use for passwords. Just recovery mechanism.
Workflow should look something like: I click amazon product link, get a new tab in anonymous context. Decide I want to buy or add to list...
Full domain *
I mean even typing in the dull domain requires an initial login or after a session expires
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.