Posts with the tag Content:
I’m suspending the kiwifarms.cc instance. Their public timeline is full of literal Nazi content, pedophilia advocacy, and aggressive trolling. I’d put this off because I hoped it wouldn’t be needed, but there you go.
The weedis.life domain seems to be a ghost ship that is intent on DoSing users by sending them a million follow notices. I’ve suspended them.
Due to overwhelming feedback from our users, Free Radical is suspending connections to Gab.com and its affiliates. If there is content there that you wish to see, please consider creating an account directly on their instance.
At their admin’s suggestion, I’m silencing (not suspending) the anime.website instance due to uncensored NSFW content. Same as always: I won’t stop you from following users there. This just keeps that out of the federated timeline.
I’m silencing the baraag.net instance, whose about page says:
This instance welcomes loli, shota, fan works, graphic violence, and any sexual depiction expressed as a piece of fiction in subject or setting. Follow them if you want to, but that’s not the federated timeline I want for us.
I’m silencing (not blocking) two instances dedicated to NSFW content. If you still want to follow users on them, please do! I mainly don’t want them filling our federated timeline, but I have zero desire to prevent anyone from seeing it who wants to. As a practical matter, I can’t financially afford to maintain mirrors of all their posted content.
When an admin fails to police their own content, or even to respond to complaints at all, it’s not reasonable to allow their instance to pollute the timelines. That’s why I’m silencing pl.smuglo.li.
One of my users complained that they received spam from @email@example.com, whose timeline currently looks like:
It turns out this whole instance is screaming with spam red flags:
It doesn’t verify email addresses1, The site that the spambot is advertising, MastodonUserMatching.tk, is a redirect to vinayaka.distsn.org (which is on the same domain as the Mastodon instance2), and The bot’s source has the same name (“vinayaka”) as the subdomain it’s spamming ads for.
I silenced our first domain this morning (and updated the status page) because a user pointed out questionable content and I agreed with their assessment.
Much has been said about that particular instance and I’m not getting into all that. It did want to comment on the rationale behind the action, though: