Changes since -alpha-4:

• Tuned filter engine
  • Bypass “filter removed comments” when in profile (mostly for admins)
  • Improve “filter users-by-instance” handling
• In <SettingButton component, reflow button below description text on small viewports.
• Display content warning if configured
• Add “Defederated” badge to user profile cards (similar to community cards) to indicate if your instance is defederated from the user’s
• Made the spoiler tag renderer prettier

Spoiler-Flaired Posts are Now Click-to-Reveal

If a post has [spoiler] (case-insensitive) in the title, only the header and footer are shown. To see the post contents, you will need to click “Reveal Spoiler” similar to “Show NSFW”.

The post form also now has a “Spoiler” toggle below the “NSFW” toggle. This will automatically add/remove the [Spoiler] flair to the post title.

Notes:

• The spoiler overlay will only show in the feed. If you click into a post, it is assumed you want to see the spoiler
• If you upvote or downvote a spoiler-flaired post, it will bypass the spoiler overlay the next time it shows up in the feed
• Your own posts will not trigger the spoiler overlay. So if you flag a post as a spoiler when you create it, you will only see that it adds the [Spoiler] flair for you.
• This is enabled by default, but you can turn it off at Settings -> Feed -> Click to Reveal Spoilers
• Unlike regular flairs which ignore bracketed words in the middle of the title (to account for [additional] details to be given), the spoiler overlay will trigger even if [spoiler] is not processed as a flair. This was a conscious decision to account for variances in how people note spoilers, but can be changed to only trigger on actual flairs at the beginning/end of the post title if people would prefer.