erica

talk account

freelance illustrator, designer, and idk buncha stuff

@kuraine's wife

avatar by karu

ascari
Last.FM Recently Played



dog
@dog

I'm really excited that cohost has tag muffles now (go read about it if you haven't seen yet!), and I think this is a great chance for us to establish an important new cultural norm.

Up until now, if you wanted to hide a post that might bother someone, the thing to do has been to CW it to hide it by default. With tag muffles, users now have the ability to preemptively protect themselves: as long as you tag something properly, users can decide for themselves if they want it hidden or not. CWs are still useful for content you think you should be hidden by default for all users, but I'd encourage everyone to think about using tags as way to let people choose what they do or don't want to see going forward.


You must log in to comment.

in reply to @dog's post:

I'm not... entirely sure, but my use case is kinda odd in that I don't use tags at all (reading or writing) because I don't want to be readily seen by people who don't already follow me/don't want to see posts from people I don't follow (rechosts notwithstanding). Part of me wants to say that the content warning filtering settings already exist and this feature is sharing the same space as that, so now people who want to be sure to block a thing have to set it in both places?

This is where I'm at too. I rarely want to take active steps to make my posts discoverable to people who don't follow me, and sometimes I positive do not want to put a post in a tag that people who are interested in that topic are likely to read. I'd much prefer to keep muffling and tagging-for-discovery as separate systems, but it seems like that ship has sailed. But I do think it would be better to have distinct conventions for discoverability-tags (e.g. '#cats') and mufflability-tags (e.g. '#cats warning').

People would need to also get in the habit of applying tags manually on shares since sharing strips the tags it appears, which renders quick shares pretty useless because it shares with no tags.