# Login required to see topic info

**URL:** <https://meta.discourse.org/t/login-required-to-see-topic-info/78512>\
**Category:** Product Support\
**Created:** [January 19, 2018, 11:33pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512 "2018-01-19T23:33:03Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [January 20, 2018, 11:07pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/16 "2018-01-20T23:07:48Z")

</div>

> [@tetra](#):
>
> You realize just because someone “can” do something with a feature, doesn’t necessarily mean they “will” do something with a feature. :S

Yes, and I’m sure you realize that even if you’re not interpreting your own intentions that way, the act of showing topic titles without allowing access to posts **is** considered to be bait-and-switch. The expected behavior by users is that **if they can see the topics, they should be able to read them**. Deviating from that user experience is widely accepted to be a dick-move, which is why Discourse doesn’t have such functionality baked-in.

The team aren’t inflexible, if someone presents a well thought-out case for a feature or change they’ll be willing to accept a PR or even build it themselves. The whole point is that nobody has been able to make a case that doesn’t fall into the above category.

---

_[View the full topic](https://meta.discourse.org/t/login-required-to-see-topic-info/78512)._
