It always makes me sad when another fedi user - and, in my experience, it is always a woman - says that they feel unsafe posting here, because of replies they get.
-
@HunterZ @neil Subscribeable blocklists are a technical issue, and I can state a number of good use cases for them.
Abuse of a blocklist by it's creator (misleading subscribers about criteria, doing a bait-and-switch after getting a subscriber base) is completely separate, and yes _that's_ a social issue. Hence my concern for categorization and ratings, and ways to prevent those from being abused to give a list a false reputation.
-
@HunterZ @neil Subscribeable blocklists are a technical issue, and I can state a number of good use cases for them.
Abuse of a blocklist by it's creator (misleading subscribers about criteria, doing a bait-and-switch after getting a subscriber base) is completely separate, and yes _that's_ a social issue. Hence my concern for categorization and ratings, and ways to prevent those from being abused to give a list a false reputation.
-
@HunterZ @neil Did I say anything about it being at the instance level? No, I did not.
The use cases all involve decisions by individual users about which blocklists to subscribe to. It certainly _could_ be used by an instance admin, but we already give them that power by allowing instance-level blocking in the first place. The social issue there isn't subscribeable blocklilsts, it's having an instance admin you can't trust not to block people inappropriately by whatever mechanism.
-
It always makes me sad when another fedi user - and, in my experience, it is always a woman - says that they feel unsafe posting here, because of replies they get.
Control over who can reply to a toot would be amazing, as a way to improve this without them needing to mute or block post-harm.
@neil remember when Mastodon asked for changes to be made to the interaction policies FEP specifically so they can opt out of implementing reply and boost control?
i remember. -
@neil I'm still looking at what's involved in creating subscribeable blocklists. The basic hook into the block functionality on the server is obvious enough, but the list itself involves learning everything about the ActivityPub protocol and the federation and syndication models. Making it useful involves having categorization and user ratings while preventing abuse of them too. Straightforward in concept, terminally hirsute in implementation.
-
@neil Can you in RL control who`s replying to words you said?
@electricfusionQ @neil this is real life too, mon.
-
It always makes me sad when another fedi user - and, in my experience, it is always a woman - says that they feel unsafe posting here, because of replies they get.
Control over who can reply to a toot would be amazing, as a way to improve this without them needing to mute or block post-harm.
-
It always makes me sad when another fedi user - and, in my experience, it is always a woman - says that they feel unsafe posting here, because of replies they get.
Control over who can reply to a toot would be amazing, as a way to improve this without them needing to mute or block post-harm.
@neil ultimately, fedi's culture of men constantly centering themselves, reply-guying, being weird and condescending and creepy to women and fems, and so forth, is a social-cultural problem. and while better tools can help to shield us from the worst of it, you can't solve a social problem with technical solutions. in other words, it's the culture of misogyny that needs to change, or nothing will fundamentally change.
-
It always makes me sad when another fedi user - and, in my experience, it is always a woman - says that they feel unsafe posting here, because of replies they get.
Control over who can reply to a toot would be amazing, as a way to improve this without them needing to mute or block post-harm.
@neil Women. Black people. Jews...
-
It always makes me sad when another fedi user - and, in my experience, it is always a woman - says that they feel unsafe posting here, because of replies they get.
Control over who can reply to a toot would be amazing, as a way to improve this without them needing to mute or block post-harm.
You can set it so only followers or people mentioned in a post can see it. Would that not achieve the same result as you cannot reply to what you cannot see.
-
You can set it so only followers or people mentioned in a post can see it. Would that not achieve the same result as you cannot reply to what you cannot see.
@the5thColumnist @neil no – it limits the audience, not what the audience can do. (additionally, the followers-only visibility doesn't do what you think it does – the audience changes with each message.)
-
It always makes me sad when another fedi user - and, in my experience, it is always a woman - says that they feel unsafe posting here, because of replies they get.
Control over who can reply to a toot would be amazing, as a way to improve this without them needing to mute or block post-harm.
@neil the problem is more the server itself, had been on two or tree server, never had the issue (i do not say the issue don't exist), just say that on server with good moderation, the issue is blocked even before starting.
-
Every time I mention this, at least one man pops up to say that they would not want to follow a woman who chooses to restrict replies.
So here, I have covered it in advance
@neil obliging of them to make us aware that they're part of the problem
-
It always makes me sad when another fedi user - and, in my experience, it is always a woman - says that they feel unsafe posting here, because of replies they get.
Control over who can reply to a toot would be amazing, as a way to improve this without them needing to mute or block post-harm.
@neil ah, if only we could persuade the Mastodon team to do that, instead of *checks notes* changing the way profile key-value fields are formatted to something unusable
-
@neil I'm still looking at what's involved in creating subscribeable blocklists. The basic hook into the block functionality on the server is obvious enough, but the list itself involves learning everything about the ActivityPub protocol and the federation and syndication models. Making it useful involves having categorization and user ratings while preventing abuse of them too. Straightforward in concept, terminally hirsute in implementation.
-
@the5thColumnist @neil no – it limits the audience, not what the audience can do. (additionally, the followers-only visibility doesn't do what you think it does – the audience changes with each message.)
I see your point. You want people to be able to see the post but not comment on it. There does not appear to be a way to do that, at least not on the web interface.
-
@HunterZ @neil Did I say anything about it being at the instance level? No, I did not.
The use cases all involve decisions by individual users about which blocklists to subscribe to. It certainly _could_ be used by an instance admin, but we already give them that power by allowing instance-level blocking in the first place. The social issue there isn't subscribeable blocklilsts, it's having an instance admin you can't trust not to block people inappropriately by whatever mechanism.
How do you know whether everyone in a blocklist deserves to be there, how do you get removed if someone puts you there for trivial reasons, etc
-
@the5thColumnist @neil gotosocial implemented such controls, mastodon didn't (i hope that changes, we need that.)
-
Every time I mention this, at least one man pops up to say that they would not want to follow a woman who chooses to restrict replies.
So here, I have covered it in advance
@neil FYI, there is a lot of discussion about what a “no replies” or limited replies feature could look like here:
-
@neil I don't really understand why the 'quotes' feature in Mastodon already has something like this, but basic replies don't. Seems like a missed opportunity.
@seabass @neil Reply controls would require changing how replies work to make them all go via the original poster's server. Currently they go directly to mentioned users (and the replier's followers), and the original poster's server can't do anything about that except reject them locally. This would also allow for fixing follower-only replies (so they go to the original poster's followers rather than to the replier's followers, which results in people seeing random fragments of conversations if they follow only some parties) and making replies federate to all users who see the original post without the need to backfill via non-standard c2s protocols (like fedifetcher does), but good luck getting everyone to implement that.
As for how Mastodon's quote controls work: they kind-of don't. I'm on Akkoma, which has had quote posts long before Mastodon and does not implement Mastodon's quote controls. Nothing prevents me (and nothing can prevent me) from quoting a quote-restricted Mastodon post, although it will (probably, I haven't tested) only appear as an ordinary post with a link to the quoted post on Mastodon, and I think also won't show up under the original post on Mastodon servers (but will on other Akkoma servers and every implementation that doesn't implement Mastodon's quote controls).
