friendly reminder that cws aren't necessarily for _content warnings_! they can be used like a subject line in an email, so that people's timelines are nicer to look at & read
@er1n It's arguably horrible UX to have to click to open every single toot, so I disagree on the nicer to look at & read. The system isn't built for this, sadly
@noiob i don't usually use the mouse when i'm on masto, so i guess i have a somewhat different experience
@er1n not saying I won't tag my stuff because I will but this is still a bad solution
@noiob @er1n I guess the point is that some people get the same reactions that you get for lewd/fetish posts from other topics as well, like food or violence descriptions, which makes the cws useful.. but the cw tool could be improved by seeing it more as a topic description/introduction and then having selective keyword mutes
@lichen I should probably just make my own frontend… I'm very interested in how the implementation for Pleroma will end up, since it's gonna focus on using it as a subject line
@noiob by all means why not, competition in implementing customization tools that protect potentially vulnerable users is only positive
@er1n remember when the feature first came about and it was called spoiler for a long time and then there was a scrap over the naming and I'm still pretty sure it's called spoiler in a lot of internals
@Trev yep it still is in the db i believe
@er1n In my fantasy, CWs would be called... something slightly different, though I don't know what, and be mandatory if you want to toot something longer than 140 characters. Also, let content-warned messages then contain markdown.