# "Sign In" vs. "Log Out" **URL:** \ **Category:** Feature\ **Created:** [2014年六月15日 14:17 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561 "2014-06-15T14:17:54Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\ **Post date:** [2014年六月15日 14:17 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561/1 "2014-06-15T14:17:54Z")
Continuing the discussion from [Icons. Icons everywhere](https://meta.discourse.org/t/icons-icons-everywhere/16543): > [@NomNuggetNom](#): > > Also, worth mentioning a small idea I had for the [Log Out button][6]. I think it could be applied to categories in the Hamburger Drop Down too. Why is the this button called _ **Log** _ _Out_ when the opposite button is called _ **Sign** _ _In_? ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2014年六月16日 02:54 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561/2 "2014-06-16T02:54:18Z")
Good point, I will fix that later tonight. Consensus seems to be Sign In was slightly better: > And > **[The secret origin of “log in”](http://www.designcult.org/2011/08/why-do-we-call-in-logging-in.html)** > > We do it dozens of times a day, every day, but why do we call it logging in? “Log in” is one of those phrases that sounds weirder the more you say it. It’s ubiquitous in online li… > but “sign in” is marginally more friendly and probably the preferred usage, though I’ll miss the nautical association ---
**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\ **Post date:** [2014年六月16日 15:35 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561/3 "2014-06-16T15:35:31Z")
There’s also “You need to log in to see that topic.” when a non-authenticated user tries to access a thread that they don’t have permission to see. (The reason this happens is because there seems to be a bug in the `/categories` view that lists all topics in subcategories for anonymous users, even if that subcategory is private/restricted to a group. I’ll post a separate bug for that shortly.) ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2014年六月16日 22:54 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561/4 "2014-06-16T22:54:29Z")
OK, those are now fixed in latest. If you find any more let me know. ---
**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\ **Post date:** [2014年六月16日 23:03 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561/5 "2014-06-16T23:03:51Z")
Updated to discourse (eedb0df) but still seeing the “Log Out” button. Even tried a completely new session (incognito mode) but no change. Am I missing a step? ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2014年六月16日 23:08 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561/6 "2014-06-16T23:08:21Z")
Not the right revision > **[Commits · discourse/discourse](https://github.com/discourse/discourse/commits/master)** > > A platform for community discussion. Free, open, simple. - Commits · discourse/discourse Takes a while for the smoke test passed build to appear. ---
**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\ **Post date:** [2014年六月16日 23:16 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561/7 "2014-06-16T23:16:15Z")
That worked. Thanks. Kind of an expectation mis-alignment on the update perhaps. If I click on the revision link when an update is available, I look at the most recent commit (which was your 288a3199f98d2a0e6e71c36f519a1c884af5c824) and assume that’s what I’ll get. In theory I should/could pay closer attention to the commit numbers but you know how humans are. 😕 Updating so quickly is probably an edge case anyway. ---
**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\ **Post date:** [2014年六月16日 23:38 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561/8 "2014-06-16T23:38:33Z")
It’s because of the “tests-passed” branch - basically, there’s a test to make sure that the browser at least renders something - and `docker_manager` pulls from there. ---
**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\ **Post date:** [2014年十月5日 22:34 UTC](https://meta.discourse.org/t/sign-in-vs-log-out/16561/9 "2014-10-05T22:34:07Z")