As an editor on the Fediverse Enhancement Proposal team I'm pleased to share a new proposal on Per-object Reply Control Policies.
Find the draft proposal here https://codeberg.org/fediverse/fep/src/branch/main/feps/fep-5624.md
Feedback is appreciated at https://socialhub.activitypub.rocks/t/fep-5624-per-object-reply-control-policies/2666
Please note that it was also subject to one of the last 12 developers meeting.
The 15 people which attended had a proposal to allow more fine granular control (which e.g. redaktor, taxiteam and the forum client will support).
Had summarized it here
Creating magic through evolution of the Fediverse. Running Ecko, a community-driven fork of Mastodon managed using the Collective Code Construction Contract (C4) by the Magic Stone Community. C4 is a protocol for asynchronous, non-blocking, distributed, problem-focused software development.