If you follow any of the #GoToSocial developers you've probably seen this going around already, but 0.17.0 of #GoToSocial will be the first release that includes interaction policies, aka reply-controls.

In the first iteration of this feature, you'll be able to configure your account so that new posts created by you will have an interaction policy set on them, which determines whether your instance drops or accepts replies, likes, and boosts of your posts, depending on the visibility of the post, and whether or not an account trying to interact with you is in your followers/following list.

So for example, you will be able to create Public posts that can only be replied to by your followers and people you follow, or unlisted posts that nobody can reply to or like, etc.

GoToSocial interaction policies will be a superset of other reply control proposals created elsewhere (and already implemented by softwares like Pixelfed and Peertube), so your GoToSocial instance should recognize interaction restrictions set not only by other GoToSocial instances, but by Pixelfed and Peertube as well.

If you're interested in reading about how this will work on a protocol level, you can take a look at the documentation here: https://docs.gotosocial.org/en/latest/federation/posts/#interaction-policy

Please note that this feature is not 100% finished yet, and may be subject to change before release. We're aware of where the headaches and difficulties are, so please don't reply to this post griping about them; we already know (and this instance is still running on 0.16.0 so no interaction policies yet).

Thanks for reading :)

Posts and Post Properties - GoToSocial Documentation

None

@gotosocial Can't wait for new release to become available  

@gotosocial

So excited for the development on GTS!

Is there anything outsiders can do to help its development, anything you need from us?

@FediThing tobi here, can't think of anything we need right now off the top of my head. It's always nice to hear that people like what we're doing though :)
@gotosocial Neat! GtS is an awesome project with amazing people working on it. It's also a ton of fun to run as a user.
@gotosocial are there equivalent docs for client developers yet?

@gotosocial

>Pixelfed and Peertube

What about Streams, will GTS be compatible with its reply control mechanism?

https://codeberg.org/streams/streams/src/branch/release/FEDERATION.md#comments

streams/FEDERATION.md at release

streams - Public domain federated communications server. Provides a feature rich ActivityPub and Nomad communication node.

Codeberg.org

@gotosocial

Thanks for including the protocol info.; was immediately about to ask about it. 😈

@gotosocial you people are amazing. i am very tempted to try this.

btw, are you aware of anyone else implementing this kind of interaction policies?

@gotosocial awesome, hopefully this will put to rest the false claims that is "impossible" in activitypub

@gotosocial Amazing work you've done here!

We look forward to implementing this, collaborating and improving federation interop between our projects.

Hey @vkc ! if you ever wish to try a different software GTS just added the feature you wish mastodon had

@gotosocial

@gotosocial Really cool! I hope it can become a de-facto standard, it seems useful in any kind of ActivityPub application.