You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm not feeling good with deciding who users of my instance could follow and read and who they don't.
From my perspective, "Block" option should be a last resort feature in case of DDoS or specifically malicious instances like "activitypub trolls".
But moderation is still needs to be done and some instances may cause problems in volumes which couldn't be solved in time by small instance staff. So some form of limitation could still be useful.
Describe the solution you'd like
I'd like to see that same form of instance-wide limitation as Mastodon implements:
This option wouldn't allow external actors from such instance to mess with local users, but still allow local users to follow anyone from such instance if they want.
Describe alternatives you've considered
--
Additional context
--
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm not feeling good with deciding who users of my instance could follow and read and who they don't.
From my perspective, "Block" option should be a last resort feature in case of DDoS or specifically malicious instances like "activitypub trolls".
But moderation is still needs to be done and some instances may cause problems in volumes which couldn't be solved in time by small instance staff. So some form of limitation could still be useful.
Describe the solution you'd like
I'd like to see that same form of instance-wide limitation as Mastodon implements:
This option wouldn't allow external actors from such instance to mess with local users, but still allow local users to follow anyone from such instance if they want.
Describe alternatives you've considered
--
Additional context
--
The text was updated successfully, but these errors were encountered: