Skip to content
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

Add autoblock spam users feature #299

Open
aramollis opened this issue May 6, 2024 · 4 comments
Open

Add autoblock spam users feature #299

aramollis opened this issue May 6, 2024 · 4 comments

Comments

@aramollis
Copy link

aramollis commented May 6, 2024

Is your feature request related to a problem? Please describe.
Related to the known "fake/spam users" problem. Human/bots users create a profile, fill in the personal URL and bio, and then do nothing on the website, or sometimes post some content. See an initial proposal for more context.

Product implemented some improvements but the main problem (autoblock spam users) remain unresolved.

Describe the solution you'd like
In order to prevent illicit content (spam messages) from being published on the platform, a mechanism will be implemented to auto-block users. When a user is blocked, their content becomes inaccessible (if they are unblocked, it is accessible again)

  • Some rules are defined that will automatically block a user if they violate it
  • When a user is auto-blocked, a report will be sent to administrators with basic data on the blocked user.
  • If the user is illegal, the administrator should not do anything.
  • If, on the other hand, it is a false positive, you will have a link to access the admin and unblock the user.

Rule criteria (admin can define how many conditions should being met to apply autoblock):

  • Users who have filled "about" field in their profile
  • Users who have published links in their user profile or comments
  • Unconfirmed email accounts

Whitelist rules:

  • Have been verified against the census on some occasion
  • Email accounts from certain domains: e.g. decidim.org, *.cat
  • Account registered/associated with a digital certificate (idcat...)

Describe alternatives you've considered

Additional context
Possible UI (WIP)
rules

  1. Allow or disable user auto-blocking
  2. Allow defining the weight (in integers) of the rules
  3. Allow defining the threshold from which the autolock is applied (>=2 for example)
  4. Add links to be able to list users who meet these rules (optional)
  5. Define whitelist rules that would bypass autoblocking

Example whitelist settings (5) that could be activated or edited:
Captura de Pantalla 2024-05-06 a les 12 43 10

@furilo
Copy link

furilo commented May 6, 2024

Just to add more context: we are half-way developing this, either we include it here or in a standalone module, but we'd like it here best ;)

@microstudi
Copy link
Contributor

Please make a PR, we'll discuss the implementation there, but we are open to it!

@aramollis
Copy link
Author

aramollis commented May 8, 2024

The list to review autoblocked users I assume should be the regular one at /admin/moderated_users?blocked=true but with some kind of filter?
I tested if you can filter by template of "justify msg" but it doesn't exist
Captura de Pantalla 2024-05-08 a les 12 49 41

Captura de Pantalla 2024-05-08 a les 12 51 03

@entantoencuanto says the actual filter "Motivo denuncia" can't be overridden but ¿maybe we can add another filter condition like "Awesome autoblocked"?

The alternative is to add CSV of autoblocked users in the email & link to /admin/moderated_users?blocked=true without any filter and admin could manually check.
In most cases will not represent a problem because there aren't a high activity blocking and you can identify by date those autoblocked (should all been blocked at the same time).

@microstudi
Copy link
Contributor

I agree that we should mark the motive as "auto-blocked" and the user should be able to reclaim a false positive don't you think?

Btw, I would change whitelist/blacklist for safelist/blocklist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants