I’m the Tesseract dev, and in the current build, any posts that aren’t your own that have [spoiler] (case-insensitive) in the post title will hide all but the post’s metadata (title, author, community, etc) and the vote/comment bar. Clicking “reveal” shows the post’s contents.

The nitty-gritty implementation details are up to you, but can we, as a group, please come together and handle this flair consistently? I would really love to be able to disable the “Show NSFW” option without missing totally safe-for-work posts due to people abusing the NSFW attribute. I get why people do that, but I’m also tired of playing “porn or spoiler” roulette.

I haven’t added this part yet, but I’m planning to put a “Spoiler” toggle on the create post form which will add [Spoiler] to the post title during the submission if the user didn’t add it manually.

Or if other apps I’m not familiar with are already doing something like this, let’s do that. Either way, let’s get on the same page.

Edit: If there are any other special-case flairs that might be handled similarly, I’m all ears.

    • Admiral Patrick@dubvee.orgOPEnglish
      12·
      2 days ago

      Definitely could, but I won’t hold my breath waiting for a feature to make it to the API. There’s enough 3rd party app support and enough people using flairs in the [flair] format, even though it’s not “officially” supported in Lemmy-UI, that I think we’d be safe implementing this.

      And should an API-level flag ever happen, then all apps would need to do is look for that boolean attribute in the Post object rather than checking the title for the spoiler flair - the rest of the handling logic can remain the same. So it’s not like we’d have to make major changes if we ever get an official spoiler flag. It would also be easy to support both so there could be backwards compatibility or for other platforms that may lack an official spoiler flag.