Remetheus

raccoon shopkeeper with a blue hat!

  • he/him

Pixel anthropomorphic raccoon head with a blue hat. Art by introdile

⇒ a story someone is telling

⇐ a beast of many nothings

⇒⇐


avatar by Mooster
header by PatchyPines
sidebar icon by Introdile
sidebar gif by Tornatics


[text ID: I sell trash and trash accessories end ID] Text is next to an amazing anthropomorphic raccoon trash merchant. He wears a blue hat and a blue hoodie. Art by Tornatics on Twitter.


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.


dog
@dog

I think this is going to be especially important for things like food, eye contact, etc. These are common, normal parts of experience that a majority of people won't have trouble with but a minority would prefer not to see. Hiding it by default is unnecessarily intrusive if there's another way for users to protect themselves - and now there is!


JhoiraArtificer
@JhoiraArtificer

worth noting too that tag muffles work on the entire tag string... so it's probably better to tag posts "food" than any more complicated things like "cw: food" or "food cw" or any of the infinite variations, because then people who need the muffle don't have to keep adding terms to their list

I personally have a philosophy of tagging the most-likely problem subjects as simply as possible for exactly this reason!


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.

in reply to @dog's post:

in reply to @JhoiraArtificer's post:

Yeah, I honestly feel like tags can serve both purposes so "food cw" tag doesn't really make sense - just tag it "food", and it works for people who are looking for food and people who don't want to see food.

Well, I may be missing something, but doesn't that assume that the poster always wants people who don't follow them to be able to find their post? I may be eccentric but I generally don't tag for discoverability because it isn't important to me and in some cases I positively do not want my post to show up in a tag – for example if I'm saying 'eh, I don't really like mushrooms', why would I want to put that in the 'food' tag where people (presumably) go to find interesting or funny or thought-provoking posts about food? Would anybody looking at the 'food' tag want to see that post? Especially if 'I don't really like mushrooms' is a throw-away sentence in the middle of a long post about, I dunno, spaceships. But presumably people who muffle the 'food' tag would still want to be warned about that post because it contains a passing mention of food. Isn't that the purpose of having distinct 'food' and 'food cw' tags?

If you're deliberately avoiding discoverability, how likely is it that people are going to need to muffle you to uh, avoid discovering it? And the CW system still exists.

Trying to bend over backwards for every possible use case seems...impractical.