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.


Blorp dev here. I’m not opposed. Just wanna point out that PieFed has official post flair support and I think Lemmy is adding it in V1?
I have to check how Tesseract does it, but maybe any [flair] should render as a post flair? I really wish Lemmy let mods edit post title so they could add/remove flairs with that format. Otherwise, anyone can use any flair regardless of what the mods intend. Maybe it’s better just to allow specific whitelisted flairs like [spoiler]?
Btw, I have a matrix group with some of the other Lemmy/PieFed Client devs. Please DM me if you wanna join.