# What could a "spoiler tag" extension look like?

**URL:** <https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767>\
**Category:** Extensions\
**Created:** [October 6, 2014, 4:05am UTC](https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767 "2014-10-06T04:05:05Z")\
**Posts on this page:** 1\
**Showing post:** 79

<div class="post-metadata">

**Author:** ![chrisalley](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/chrisalley/32/906_2.png) [@chrisalley](https://talk.commonmark.org/u/chrisalley)\
**Post date:** [February 7, 2019, 7:18am UTC](https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767/79 "2019-02-07T07:18:36Z")

</div>

[Discord recently added](https://support.discordapp.com/hc/en-us/community/posts/360030058672/comments/360004273371) the ability to put “guardrails” around spoiler text to mark it up. E.g.

`The film reveals that ||the bad guy is actually his father||.`

Discord uses [a flavour of Markdown](https://support.discordapp.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline-) in chat conversions; the addition of guardrail syntax here makes sense since it represents something. Perhaps it could be extended into block syntax like this:

```auto
|||
Big spoiler here.
|||

```

In any case, an inline spoiler syntax would be useful in chat conversations and comments systems, perhaps even more so than a block spoiler syntax. The Discord inline spoiler syntax is bit easier to remember than the `!>spoiler<!` syntax proposed earlier as it doesn’t require remembering the specific order of the opening/closing characters, plus the characters feel more meaningful.

---

_[View the full topic](https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767)._