Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Block users #17453

Closed
qwerty287 opened this issue Oct 27, 2021 · 4 comments · Fixed by #29028
Closed

Block users #17453

qwerty287 opened this issue Oct 27, 2021 · 4 comments · Fixed by #29028
Labels
topic/moderation features for moderating spam, abuse, ... type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@qwerty287
Copy link
Contributor

qwerty287 commented Oct 27, 2021

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:

  • notify the user by mentioning (in general, notifications should be suppressed)
  • create issues/PRs in repos owned by this user (except if the user is added as collaborator)
  • add you to an org or as a collaborator
  • follow you
  • maybe hide personal information like email, full name, profile picture (however, you could just logout and view the profile)

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

@delvh
Copy link
Member

delvh commented Oct 27, 2021

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.

@lunny
Copy link
Member

lunny commented Oct 28, 2021

You can prohibit a user login on admin panel -> users.

@qwerty287
Copy link
Contributor Author

qwerty287 commented Oct 28, 2021

@lunny
Yes, but not if

  • you aren't an admin
  • they are on another instance (once federation is implemented)

@techknowlogick
Copy link
Member

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)

@lunny lunny added type/proposal The new feature has not been accepted yet but needs to be discussed first. type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels Apr 25, 2022
@6543 6543 added the topic/moderation features for moderating spam, abuse, ... label Aug 9, 2022
lunny pushed a commit that referenced this issue Mar 4, 2024
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>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
topic/moderation features for moderating spam, abuse, ... type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants