-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Allows users to block instances individually #917
Comments
A lot easier to implement after #939 is merged |
PR #939 is merged. |
Nope not related. The feature request is that individual users should be able to block instances |
Owh.. Updated title. |
Yeah, I'm at 209 blocked communities right now. lol Edit: How are we defederated with lemmygrad but not with hexbear though? |
Is your feature request related to a problem? Please describe.
Some instances federated with either have content, users, magazines, or something one would not like to interact with. For example an extremely political instance might not be sharing any content one would like to interact with.
Describe the solution you'd like
Allows users (not on instance level) to block anybody and everything from an instance.
Describe alternatives you've considered
Manually block everybody and everything from an instance. However this is time consuming.
Use a client (do such clients exist?) that automatically block depending on which instance the content is coming from.
Additional context
There is a "block domain" feature, but that seems to only block posts with links to instance. For example one creates a post that has the URL https://somebodysinstance.com/some/path and one has blocked the domain "somebodysinstance.com", then that post won't show up.
The text was updated successfully, but these errors were encountered: