I’m the Tesseract dev, and in the current build, any posts that aren’t your own that have [] (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 [] 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.
Can’t link to the posts directly to demonstrate since the spoiler overlay is only shown in the feed. It’s assumed if you click into the post you want to see the spoiler. I suppose I could change that, but the behavior aligns with how the NSFW tag works.
To give an example of how it works in the feed, here’s a search link that should work (it’s what I used to make the post screenshot): https://tesseract.dubvee.org/search?type=All&q=posts%3A[spoiler]
Correct. While that wouldn’t turn into a flair (only
[flair text]at the beginning or end of the title will be used as flairs), it will trigger the spoiler overlay if[spoiler]appears anywhere in the title. I did this consciously to account for inconsistencies in some of the spoiler usage I’ve seen. It could easily be changed to only trigger on actual flairs (at the beginning or end of the title).What happens if someone direct links you to a NSFW post? I was thinking about detecting if you clicked on the post vs if you were direct linked to a post, and requiring a NSFW toggle based on that.