Alex @alex@dads.cool

In addition to some overdue domain blocks, the Code of Conduct at https://dads.cool/about/more 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 dads.cool github page where changes to the code can be tracked

#dadmin

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)

#dadmin

A lot of good fixes coming in the next #hometown 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! #dadmin

Gonna block qoto.org on this instance later this morning when I’m at my desk.

Their forked version of mastodon implements a feature that allows accounts on their instance to follow locked accounts—even if you reject a follow request from a qoto user, they can see all your public-level posts on their home timeline.

This is a breach of trust to users of other instances and provides a vector for stalking and harassment, as users may not know who is following them.

#dadmin

Thinking about adding an FAQ to dads.cool’s about page, including the obvious “Why not regular mastodon?” and “why dads and just not parents?” #dadmin