Implement spoiler tag support

[aeharding]

:::spoiler

(stuff here)

:::

is supported by lemmy. It appears to be custom spoiler markup? So might need to implement our own markdown plugin. :/

[devzzm]

Seconding this

[ZarK]

Second this, we’re now starting to get some active movies and TV show discussion communities, and it would be very nice to not see the content of the spoilers when using Voyager.

[jachan]

Hey Alex,

Would love to take this and try and implement spoiler tag support, if no one else is working on it.

[aeharding]

I would appreciate that. mdast parsing is not my forte.

[80avin]

I am looking to work on this, but looks like there's no defined format of how to define spoilers in markdown.

Similar discussion is going on here: LemmyNet/lemmy-ui#687

I think we can support reddit's spoiler ( >!spoiler!< or >!spoiler line ) and lemmy's spoiler both.

[boozook]

I have to clarify the format of the spoiler text given by the topic starter.

:::spoiler title

(stuff here)

:::

[DakshG07]

Don't see anyone actively working on this, so I'll try to take a stab at it.

[aeharding]

Okay, thanks @DakshG07!

If it helps, my investigations in the past led me to the following info:

• Lemmy uses https://github.com/markdown-it/markdown-it-container to parse spoilers.
• No perfect alternative for remark.js exists. There is this but its outdated. There's also remark-directive but it only accepts a custom format slightly different than lemmy's format and is inflexbile.

Which leads me to the thought, unless I'm missing anything, that either

1. Lemmy should change their spoiler formatting to be something more compatible between various markdown parsers, or
2. we need to build our own remark.js lemmy spoiler plugin.

[80avin]

@DakshG07 You're welcome.

I have started on this few weeks ago, but learning about unifiedjs, remark, mdast, micromark, etc to make a spoiler plugin is taking more time than I can dedicate.

Then, since it will be a set of plugins for remark, mdast, micromark, I thought of creating a separate package, which again is another rabbit hole, so more time.

Anyways, it is being a good learning experience and I might require 2-3 weekends. But if you want to try your hands, I'm happy to concede.