-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Block users #17453
Comments
I think this shouldn't even be restricted to user-to-user interaction, any of the four possible scenarios between users and organizations should be possible. |
You can prohibit a user login on admin panel -> users. |
@lunny
|
I believe some of the grant application has a portion set aside for tasks such as this (and as you mentioned regardless of federation it'd be very beneficial to have on shared instances such as codeberg) |
Fixes #17453 This PR adds the abbility to block a user from a personal account or organization to restrict how the blocked user can interact with the blocker. The docs explain what's the consequence of blocking a user. Screenshots: ![grafik](https://github.com/go-gitea/gitea/assets/1666336/4ed884f3-e06a-4862-afd3-3b8aa2488dc6) ![grafik](https://github.com/go-gitea/gitea/assets/1666336/ae6d4981-f252-4f50-a429-04f0f9f1cdf1) ![grafik](https://github.com/go-gitea/gitea/assets/1666336/ca153599-5b0f-4b4a-90fe-18bdfd6f0b6b) --------- Co-authored-by: Lauris BH <lauris@nix.lv>
Feature Description
I didn't find this feature request in the issue tracker, however, I think this is a pretty popular request, so if this is a duplicate, I'm sorry.
I think it would be good to have a "block users" feature, especially if federation is coming because then users could register on any instance to notify you. If a user blocks another user, it shouldn't be able to:
GitHub docs about this feature on GitHub: https://docs.github.com/en/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account
I found a ref on Codeberg: https://codeberg.org/Codeberg/Community/issues/373
Screenshots
No response
The text was updated successfully, but these errors were encountered: