Is it okay to make a thread about a potentially (or, in the particular case i'm thinking of, almost certainly) discomforting topic as long as we mark it as such in the title and the first post? E.g. the title could be something like [Heavy content] Has there ever been a case where this happened?, and the first post could contain something like:
Warning: This thread discusses [more detail on the specific heavy topics the thread deals with].
I'm wondering if there's ever been an instance of[…]
An issue i can see with this is that the potentially discomforting content, if it happens to be in the foremost bit of a reply, would get bridged to Apionet without any marking, but i could see this being worked around by requiring people in the thread to insert some gibberish at the front to offset the content past the point of the cutoff.
Optical Character Recognition, Geometric Shapes, Ornamental Dingbats, and Alchemical Symbols are all pretty cool, but so are Specials and Tags. But i think my favorite is Variation Selectors Supplement.
Based on my personal experience, having separate tags for feature requests and bug reports leads to occasional bickering about what counts as which, distracting from discussion of the actually important parts of them.
On the other hand, distinguishing between what is and isn't a problem is important—after all, if something doesn't fix a problem, then it won't end up being used and will just end up bloating things. Having a single tag for issues would encourage insightful discussions about whether something is really a problem.
I've personally found that feature requests tend to be issue reports in disguise, even if the reporter doesn't realize it—usually, it's completely possible to reword them to show how they would fix some sort of problem. If that's not possible…well, it's not really worth implementing, is it?