Which brings me to CWs on here. My first observation is that, that it is easy to add them. The functionality is literally one extra click, which adds a negligible amount of time to your posting.
There is also none of the issue regarding sharing the CW function with other functions like comment or snark (although that may of course still develop).
1. Where does my right to access/avoid other people’s posts begin and end?
2. Where does other people’s right to access/avoid my posts begin and end?
3. What is the most mutually considerate way to accommodate everyone’s needs?
So when the poster over on the other place said (by way of example) “But CW: Politics? Not a world I want”, I’m responding “Why ever not?”
If it takes me literally a nanosecond to slap a “Politics” wrapper on my posts, and it takes you literally another nanosecond to click on that wrapper to unwrap it, what have either of us lost in this world?
I will still be able to write what I want and all my followers will still be able to read it. The one thing that I’m not doing is forcing them to read stuff they may not want to read.
And while people’s individual decisions not to read stuff are ‘t always unproblematic (more about that further down this thread), neither is me thinking that I have a right to force my content on them.
So, like@[email protected] I have come to think of CWs as “content wrappers” rather then “content warnings“.
And here are two examples for why that works for me.
@TheCybermatron The whole idea that, by posting some plain text, you "force" it on people, as if readers aren't competent to monitor their own boundaries and protect their own mental health, goes at the heart of my objection against CW'ing normal discussion. It's denying agency to readers. I find it patronising.
As an autistic person, I have been patronised enough, and I would extend to others the courtesy of presuming them competent.
CWs should be reserved for extreme material.
@TheCybermatron Tagging @Teri_Kanefield
Teri: this long and very helpful thread might provide some details for the blog post you are working on.
I am having trouble figuring out how to access it. When I click, I don't see a thread.
Me = stupid newbie
@TheCybermatron It is not easy to read CW'ed threads/discussions, though. You have to click on each of up to dozens of individual posts to expand them, which is RSI-inducing.
There is an option hidden in the settings to auto-expand all CWs (thereby making them all ineffective). But that only applies to your own instance. Due to how federation works, complete threads can usually only be read on their native instance, so if that's not your own, you have to click them all again.
I thought the 'eye' (more or less) icon in the header of a column displaying a thread, opened all the CW content, without doing that globally in preferences?
Might be interface or version specific though, perhaps?
Thanks for offering this conceptualisation. I find it very helpful.
"Recommender system"; helping us in navigate communication where different people use different typologies. This helps me think about CWs.
@TheCybermatron Um you have well and truly overloaded my feed with dozens of posts which makes me pretty sad. :(
Why not do one post and reply unlisted for the rest? Then I only have to see the first one, if I choose to expand it.
If you put a CW on your posts it helps other people. If you don't like seeing CW's there is an option in preferences to always expand them on your own feed.
@TheCybermatron
Re: politics in particular - speaking personally, I'm actively interested other people sharing their lived experience or unique perspectives on important topics. I wouldn't be bothered if someone chose not to CW that sort of thing.
But, I do find certain kinds of national news/electoral politics type stuff exhausting just because of the sheer volume. If someone was posting minute-by-minute election updates or something, I'd definitely appreciate a CW there.
I agree wholeheartedly with what you said.
In particular it was a hard lesson to learn CWs have been weaponized against POC. And I've seen virtual civil wars in here in previous years (even before this new users wave) where those are involved. They're just as bad as you think.
So the rules would be:
1) In general, use CWs. If you don't understand why you have to use a CW, then the advice is aimed at you, specifically. I don't give a damn whether you understand or not; just follow the rules and don't be a crybaby.
2) You're not obligated to use CWs if you're an oppressed minority and are talking about your experiences of oppression.
3) If you're NOT part of the oppressed minority in question, you have NO RIGHT to ask them to CW their experiences with that particular part of oppression. It would be nice, of course, but the oppressed minority in question has the moral high ground to say "this needs to be seen." It's their moment; suck it up.
To generalize, CWs are mean to protect oppressed minorities from everyone else; NOT protect everyone else from them, otherwise it becomes segregation. It's a one-way filter.
@yuki2501 what if people within a minority don't want to be repeatedly reminded of their oppression, and would prefer the ability to skip such posts.
E.g. should I as an LGBT person need to see posts over and over about LGBT rights being taken away when I'd prefer not to?
Content can still be seen with a CW. I don't see it as a filter but a subject line.
Hi, great post. I see CWs as a mechanism of lowering the volume - or at the very least giving the user the volume control to decide how soft or how loud they want engagement - across a range of subjects.
That's a rather sloppy way of saying that in the other place the louder voices seek to dominate discussion - and when they don't get what they want, the volume gets even louder, language becomes uncivil, and engagement breaks down. 🧵
@GreenCarnation2 @TheCybermatron
Use CWs to "lower the volume" ---- an excellent way of putting it. Agree fully.
:-)
Same here.
@TheCybermatron My thoughts are: I can't read the thread w/out clicking "show more" a few (dozen, you did say long :-) times.
that's a UI issue and a barrier and I just didn't do it. sorry, I am c urious about what you have to say, but not enough to click on all the comments.
@glowrocks And the fact that this is now your choice was exactly the point I was trying to make 😉.
But I agree that it would be more user friendly, if on threads, you would only have to click once to unwrap the whole thread. Not sure, if that can be changed, though. Might be necessary to use blogs more again.
Would be nice to have that option, of CWing the whole thread. That would require some mechanism for re-inserting the top-level CW when a lower-level post gets boosted.
But I agree, the need to constantly re-affirm one's willingness to read the content is somewhat jarring. I can cope with it, but it ain't perfect. This certainly won't stop me from reading a thread though ...
My exact feelings. Learning how to use CWs to me was a way of absorbing a key aspect of mastodon culture & unlearning bad twitter habits.
Wow, you sure know how to thread a long thread. :-)
Seriously, your thread is super helpful, a thoughtful & nuanced analysis of the use of CWs, pointing out some of the overlooked overtones and undertones of CW conventions.
Thank you, you have helped this new mastodon arrival in sorting out his own CW practice.
It is indeed a vexed question. Some marginalised communities make a powerful case, but I am inclined to take your view. I suspect that it may depend which instance you 'live' on too. The problem being that once you go federated with replies, the custom and practice becomes as diverse as the people making up some of the communities.
I know the developers are discussing this issue on Github, with a view to possible rename which may take some heat out of it.
@TheCybermatron, thank you from my heart. I've been pondering about CWs lately and your thread very eloquently summarises my thoughts so far as well as dives into details and conclusions, I feel my own train of thought was navigating towards too.
thank you @hook for pointing at this and thanks @TheCybermatron for writing this.
It's very well articulated and I'm especially thankful for thoughts on BIPOC's weaponised cws argument with which I struggle.
I want to contribute a little thought about the fact that the 🧵is about the space called 'home timeline'. I agree with everything written, but there's no consideration of local timeline and how posts are CWd according to that 'space'.
as a mod/admin trying to convince people about what you wrote I'm faced with multiple possible configurations between marking posts visibility (public vs unlisted) and CWs. I actually think that while CWing for your followers it is even more crucial to think of a community on your instance that is reading the local timeline.