# Must reply to see the hidden link / Content

**URL:** <https://meta.discourse.org/t/must-reply-to-see-the-hidden-link-content/71382>\
**Category:** Product Support\
**Created:** [04.Октябрь.2017 07:05:50 UTC](https://meta.discourse.org/t/must-reply-to-see-the-hidden-link-content/71382 "2017-10-04T07:05:50Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![fantasticfears](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fantasticfears/32/119608_2.png) [@fantasticfears](https://meta.discourse.org/u/fantasticfears)\
**Post date:** [26.Ноябрь.2017 13:38:25 UTC](https://meta.discourse.org/t/must-reply-to-see-the-hidden-link-content/71382/7 "2017-11-26T13:38:25Z")

</div>

We had a conversation on email but it’s best we keep it here.

A year ago, I’ve developed a plugin that can hide content unless replied to the thread. You can find it here: [GitHub - erickguan/discourse-reply-required · GitHub](https://github.com/fantasticfears/discourse-reply-required)

It allows a special markup like `[reply-required][/reply-required]` to encapsulate a content. The content reveals until the user replies to the thread. But it doesn’t hide information to search engines.

Along the way, I felt it’s cumbersome to design it even I had a client who used it extensively. Mainly reasons are:

1. Visual clutter and has nothing to do with cultivating community, even though it looks like people engage.
2. It takes quite effort to hide the information. And it takes more time to even load content. How does that benefit to community since content is the key.

For the very same reason, we have stopped to invest on it.

Despite the story, the plugin can be tweaked to work.

---

_[View the full topic](https://meta.discourse.org/t/must-reply-to-see-the-hidden-link-content/71382)._