https://twitter.com/pati_gallardo/status/1590485665535643649?s=46&t=hpE2Unzsn-9qKirLfo3tYA
@patricia thanks for writing this.
Folks here on #Mastodon should read this, and take this seriously.
Clearly, there's a culture around how things are done here at Mastodon, but maybe there is a better way to teach folks about that culture instead of blocking/banning folks outright.
If #Mastadon is to be a place for well-meaning folks on the internet, threatening people may not be the best way forward.
And it is hard to know who means well, but @[email protected]'s call out is pretty clear cut #IMHO
an instance where "well-meaning" is not clear-cut:
I have refrained from posting anything about last night's elections here in the US, because I know I would be dinged about CWs. That makes me not want to post about elections/politics.
That does not feel very free-speech-y.
But I can also easily imagine discourse around US politics and elections getting out of hand (as intentioned by the OP), so a CW may not be a bad idea for all things politics (?). I dunno!
@krishnavp while CW does imply upset. I think the use on Mastodon has evolved past that. And in some instances/interfaces, it's actually called a "subject line".
This thread may provide greater insight:
https://someone.elses.computer/@TheCybermatron/109320168604846395
@krishnavp but as a summary. I think of it likes this. I don't live in America. So I don't care as much about US politics. Therefore I may skip over a few posts that have a CW of US politics. Otherwise I'd have to skim all of them and it gets annoying.
On a more mundane note. I'm no longer a PhD students. If people are looking advertise to PhD students a position, a CW for that also keeps me from getting spammed irrelevant stuff.
Don't see the downside.
@diego to clarify: I would have no trouble if someone used a CW for their posts.. no matter the subject (eg, PhD Positions posting). But I am not going to go ask them to add CW if I think they are missing one.
I would certainly not do this as a mod, unless I have explicitly called it out in the community guidelines of the instance I run. And even then I would be mindful of how I communicate it. 🙂