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.

Public posts may be discoverable and accessible by visiting someone’s profile, but this qoto feature (and the mastodon pull request that does the same thing) posits that users are entitled to view someone’s public posts at the moment they’re posted. That’s wrong. Denying a follow request, but not blocking someone, means you do not consent to giving them instantaneous and convenient access to reply to or engage with your posts. Just because they’re public doesn’t mean they’re for you.

Show thread

The people replying to this saying “but your public posts are easy to get already, just grab the RSS feed or remember to visit the profile!” underestimate the value of slightly inconveniencing users whose follow request you denied. Nothing is easier than something being in your home timeline, across all masto clients, to reply to or boost or like or bookmark.

@alex those people all coincidentally hang out on perfectly silencable instances themselves, amazing how that works.

If you don't want someone to reply to your toot, just block them. Or better yet, mute them and let them reply for the benefit of other people if you don't want to read them.

I'm getting notes of DRM from this.

@alex To say the obvious: it clearly makes a difference for the people wanting to be creepy. They always could just use RSS or public posts, but they still insist on the new "feature".

Sign in to participate in the conversation

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