and are now silenced on; our posts will reach them, but users will only see interactions from users they’re following on those instances, not anyone else. I’m only taking this step on right now, not the other instances I mod/admin. I am just not going to deal with a fresh story of a Black or Asian person wrongfully suspended by an unaccountable green mod team literally daily. Fix your shit, WB. is immediately suspended on,, and bigshoulders because of this.

any component part of the department of homeland security of the united states has nearly boundless potential of being a vector of terror and abuse. i don't care if a nerd you like works there. they are not going to see our posts.

I am not immune from making stupid admin statements but suspending a trans journalist for defending their right to exist and positioning it like you’re putting them in time out so they can return to some kind of “civility” is pretty obscene.

I’ll be silencing on,, and tonight—my hope is that j.h implodes before that i need to upgrade that to a suspension.

i've undone the suspension, they've changed their tune on hosting terfs. hooray for peer pressure!

banned (nazi shit).

if you're looking for nazi instances to block, a good tip is to use the custom emoji interface and do a search for instances with "windmill" emojis. you'll see what i mean.

I don’t block any of the big open-registration I servers because I’m still interested in growing,, and (not forever, but for a while) and discoverability is very important; most new users come from somewhere big, even if it’s literally just for a day or something.

That being said, if I start getting a lot of reports about a server that doesn’t appear to be actively moderated, I will definitely make moves to protect users.

blocked social dot wideboys dot org for weirdo shit obvious in a cursory glance

the instance with the csa apologist was already suspended here, more than a year ago

suspended for pleroma nonsense (an @everyone tag that affects masto accounts)

yes i'm aware of jon's the cure post and i am considering next steps

if the current trajectory continues we are not *super* far from having to bump up d.c to the $42/month hosting tier, probably in a month or two

I’m planning to put some time into updating the blocklist here today (and making sure matches). If any admins want to DM me their list that would be helpful, I know a lot of foulness has popped up this month

hey I normally post mod actions local-only but @radicalrobit brought to my attention that some scummos are getting to other instance’s posts because hasn’t suspended them yet. I just suspended 6 accounts (gotta love open registration instances) of one of these users. Please let me know if anything else like this pops up I’ll act as quickly as possible. For d.c users, I post mod actions with the hashtag . Sorry for leaving the door cracked to creeps

anyway our blocklist is on, i do not have as much time to affirmatively search for urls to block but if i hear about something i will do something. new blocks are announced as local-only posts with the tag

Show thread

per Eugen, truthsocial disabled all federation features. so if you're wondering if is blocking it, there's nothing to block.

suspending as the url is being used to impersonate users in polls (and possibly elsewhere). h/t to @lawremipsum for discovering the issue in the weirdest way possible (ballot-stuffing in a poll where “lmao” was the winning answer)

alrighty i'm gonna suspend because among other things, their TOS uses the standard of "deserves it" for whether violent and abusive language and posts are ok (cw screenshot from TOS that describes graphic violence)

In addition to some overdue domain blocks, the Code of Conduct at has been updated with the following changes:

· a table of commonly-used CWs if you're new to Mastodon

· a statement explaining that multi-user instances without codes of conduct (or with codes of conduct that do not explicitly forbid harassment) will be suspended

· a link to the github page where changes to the code can be tracked

Updating to hometown 1.0.4+3.1.4 momentarily, expect only a couple minutes of downtime.

Fixes include:
-"Not Available" image attachments will now reattempt to download (a mastodon bug fixed in 3.1.4)

-pinned local-only posts now stay local-only (thanks @darius!)

-in apps, replies to local posts will stay local, and unique posts will be local-only if that's what you have as default in the web UI (see details in screenshot)

A lot of good fixes coming in the next update next week, including a fix for the “not available” image preview bug which affected pretty much the whole fediverse, as well as several fixes for local-only posting, including local-only pinned posts. Thanks for the hard work, @darius!

Show older is a Mastodon instance for dads, running the Hometown fork of Mastodon.