3 ms·
> I always hated how the "Login" button is smaller on every website than the "Sign Up" button. I always assumed that was because it's the least common flow. On
by JoshTriplett 3mo ago
> I always hated how the "Login" button is smaller on every website than the "Sign Up" button.
I always assumed that was because it's the least common flow. Once you've signed up, you're logged in, so the only time you should ever need the "login" button is on a new computer, or after logging out to switch accounts, or if the service offers a "remember me" checkbox (don't do that) and doesn't check it by default (definitely don't do that), or if the user genuinely wants to not be remembered (e.g. they used private browsing).
If you're having to use "login" on any regular basis, something in the overall flow needs improving.
- interloxia 3mo agoI love clearing cookies.
- dzhiurgis 3mo agoThey can still follow you
- two_handfuls 3mo agoNo reason to make it easy for them though.
- gunalx 3mo agoYour tokens should defiently have expiry times on the range that you would need to login again.
- londons_explore 3mo agoI would prefer a 999 year login cookie. A well designed browser stores the cookies with similar security to the built in password manager anyway
- ffsm8 3mo agoThat's not true, you need to provide a password to read the passwords saved in the browser whereas cookies can be read without any hassle from the developer tools Cookies can also be queried programmatically, whereas passwords need to have the users auto fill active and interact with the input element Most extensions have effectively full access to your cookies, not to your passwords - which is a real attack vector (session exfiltration) which is actively being used by had acteues There are ofc server set cookies which are not programmatically queryable, but that's not the norm (and they're still visible via the developer tools, so the core statement remains untrue)
- watermelon0 3mo agoI’m quite sure that server set cookies are the norm for authentication, at least where they are set from the server side.
- mmmmbbbhb 3mo ago> Cookies can also be queried programmatically, Misleading statement, essentially untrue. > Most extensions have effectively full access to your cookies False. > There are ofc server set cookies which are not programmatically queryable, but that's not the norm That is the norm for login cookies. > and they're still visible via the developer tools, This is irrelevant to the argument.
- layer8 3mo ago> the only time you should ever need the "login" button is on a new computer, or after logging out to switch accounts That’s still more frequent per customer than signing up. It only makes sense when prioritizing growth over your long-term customers.
- xboxnolifes 3mo agoEvery website I've signup for I've also logged into at least once. Usually more than once. Frequency isn't the reason, it's optimizing for sign-ups. Once you get someone to sign-up, they're going to login even if the button is a little smaller.
- deleted 3mo ago[deleted]
- pluralmonad 3mo agoYou sign up once and login an arbitrary number of times. Not sure how signing up is ever the more frequent path. I've signed up for things I use maybe at most twice throughout a lifetime. Logins I couldn't even begin to count.
- QuantumGood 3mo agoIt's an "absence of light" pattern (as opposed to dark pattern). Creating a very common tech support issue; sometimes "login" isn't even visible.
- sideras56 3mo agosometimes websites design sign up button as primary button, and login as secondary