True Block

[Architect]

@fbpbdmin

• say, A always bothers B.
• B does not like A keeping posting to his/her topics.
  B really wants to disallow A to comment in his/her topics

this is becoming a more and more wanted feature/function in our forum…

This is for a community site you administer and have moderators for?

If A is always bothering B this seems like a reasonable feature request to be able to prohibit A from commenting on B’s topics. There are some other options such as B can post in closed restricted access categories or A could be banned from the site. First step seems like should be asking A to stop posting on B’s topics, or be issued official warning to not do that from moderator could help.

Here is post in related topic about their reasoning for current structure:

How to do a "mutual ignore"?

Yes, a large part of the reason Discourse has resisted stronger user-enactable block is that the need for a member to block another is fundamentally a threat to community cohesion. If the moderators can take action to resolve the tension, that’s a healthier outcome than quiet simmering. The ‘ignore’ feature was implemented due to a dispute that originated entirely outside the forum, making it painful for Member A to read Member B’s posts. Also: read-blocking would be even more of a farce on Di…

If a new feature was implemented allowing members to stop any other member from commenting on their topics, seems there would be a risk of that causing additional problems.

Most important is for there to be competent moderation, so if someone has a request that someone else not bother them that will be honored. If one person is being bothered on a regular basis there are likely other people also being bothered by the same issue that needs moderator intervention to resolve.