Gentle Reminder 💚🐘:

✅​ If you wish to warn your audience about a topic that you deem disturbing, annoying, spoilers, and so on, DO use Content Warnings to wrap your own posts. Here's how: https://infosec.exchange/@Em0nM4stodon/109282181601490676

✅​ If you do not wish to see posts about certain topics in your own timelines, DO use Filters to hide these posts for yourself. Here's how: https://infosec.exchange/@Em0nM4stodon/109323462169819778

❌​ But DO NOT, tell people in reply they should hide their own posts!

Respect what others wish to post about.

You have the options to Filter, Mute, Unfollow, Block, and even Report if a post is breaking the Server’s Rules.

Stay kind, and let others use their own voice 💚

#TinyMastodonTip #Mastodon

Em :official_verified: (@[email protected])

Tiny Mastodon Newbie Tip 🐘: Content Warning (CW) is used quite liberally here. It’s an amazing Mastodon feature! Use it as often as it might be helpful. You can use Content Warning to hide a toot (post) your are writing that: - discusses or displays topics that might disturb other users (ex: violence, nudity, mental health, food, etc) ⚠️​ - discusses or displays topics that you think could be annoying or irrelevant to other users (ex: twitter, local politics, very long post, whom-who-shall-not-be-named, etc) 🔕​ - discusses spoilers of a tv show, movie, video game, or book 🤯​ - hides a joke you want to create a special surprise for! :awesome:​ HOW TO❓​ 1. On desktop, below the toot writing field, click on “CW” in the menu. The button’s icon and label may vary for mobile apps, but it should be there! 2. This will add an extra title field above with “Write your warning here” (or similar label). 3. Write the warning (what people will see) for your toot (ex: “Spoiler Star Trek Discovery Season 10!” or “Discussion of violence:” etc). 4. Write your toot normally in the field “What’s on your mind?” (or similar label) and Publish! 5. People will have to click on “Show More” to see the content of your toot. 6. Magic!✨ #TinyMastodonTip #Mastodon

Infosec Exchange

@Em0nM4stodon

I think it's reasonable to *politely* ask someone whose toots you see to cw a particular subject that they wouldn't otherwise think to cw.

If they say no, then one can still break out the filters and so forth. But they might also just be like "oh, yeah, sure! No worries!"

@Em0nM4stodon

Also sensible: "Hey, folks who see my toots, should I cw [x]?" or "Hey, is there anything you wish I'd cw that I don't?"

@aearo
@Em0nM4stodon
I think the problem is that while you will no doubt be asking someone to CW something in good faith, there's no way to know whether others have already advised them to CW that or similar content in the past, be it once or 100 times, and they either forgot or chose not to CW.

There's a risk of unknowingly dogpiling there, which I have seen happen plenty of times already here.

@IntlLawGnome @Em0nM4stodon

That's a good point! But I still think a polite ask is generally reasonable.

I guess maybe if you're in that situation, where you're getting bombarded with cw requests, that's a sign it's worth saying something in your profile or a pinned post about your cw policies.

  Maybe a distinction should be made here between accounts one intends to have real interactions with, and accounts with a zillion followers who probably won't even realize you exist. It's the latter who are most likely to be dogpiled, I'd figure, and the former who are most likely to go "sure, friend!"

@aearo
@Em0nM4stodon
Frankly I think that "if you're getting dogpiled maybe you should listen to everyone scolding you" is not a perspective I can get behind. But people will do what they want to do, so I won't push the point.

I just ask that folks remember the human on the other end of the interaction, and remember you don't know everything about their experience & intentions. Which I know everyone in this conversation is trying to keep in mind. 👍

@IntlLawGnome @Em0nM4stodon

Yeah! I don't think we really disagree that much.

I dunno if I can get behind that perspective much either - I'm just saying, if you're getting a ton of people with the same expectation, might be worth giving them an FAQ so their expectations will be different. And then they'll stop bugging you, maybe. 😉