My issue with CWs is that you are deciding for yourself what others should consider "sensitive" content. The trouble with that fir me is there are some people who are sensitive about really niche things. I understand putting a CW on NSFW media; because that could get you in trouble at work. But putting CWs on anything else is a bit over-the-top for me. I just saw someone asking for CWs on holiday posts because it makes that person sad... Seems a bit much for me! 😅
@klaatu I like that idea actually. Its true that a title of a book or movie is also a "Content Warning" usually, but I like the idea of a Title or Subject usage as opposed to some protection mechanism. Eventhough functionally they are very similar to CW.
@klaatu @davidpgil seeing how society works these days, we'll get clickbait title instead of real one.
Moreover, it's an UX nightmare. What if the user want to always have them expanded but still collapsed for real CW contents.
@davidpgil @klaatu #usenet really *was* the original, longer posting version of #mastodon
masto is just generally easier to manage, web based and API-ed.