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

Users autoblock feature #305

Draft
wants to merge 48 commits into
base: main
Choose a base branch
from
Draft

Users autoblock feature #305

wants to merge 48 commits into from

Conversation

entantoencuanto
Copy link
Contributor

[WIP] Feature to autoblock users.

The description is pending, once the code is better organized it will be added

Base automatically changed from develop to main August 1, 2024 09:33
@aramollis
Copy link

@microstudi we finished the job here some months ago. Anything pending to be able to add to next release of Awesome?

@microstudi
Copy link
Contributor

@microstudi we finished the job here some months ago. Anything pending to be able to add to next release of Awesome?

This PR is marked as a Draft, also it does say "WIP" in the description and, with a quick look, it does not have any specs. Please fix things and I'll review it!

@aramollis
Copy link

@microstudi we finished the job here some months ago. Anything pending to be able to add to next release of Awesome?

This PR is marked as a Draft, also it does say "WIP" in the description and, with a quick look, it does not have any specs. Please fix things and I'll review it!

Can you complete @entantoencuanto ? Tx!

aramollis added a commit to PopulateTools/decidim-module-decidim_awesome that referenced this pull request Dec 3, 2024
Updated the README to reflect changes introduced with the PR for the Autoblock feature: decidim-ice#305, addressing issue decidim-ice#299.
@aramollis
Copy link

Can you review @microstudi ?

@microstudi
Copy link
Contributor

Sorry, I didn't notice this @aramollis. I see that you have a README updated in another place, can you port it here? meanwhile I'll test and review this between this and the next week

@aramollis
Copy link

Sorry, I didn't notice this @aramollis. I see that you have a README updated in another place, can you port it here? meanwhile I'll test and review this between this and the next week

I'm not sure where should be defined and I tried to add in the main readme of the module.
I think I haven't access everywhere, so I copy here, and you or @entantoencuanto can put in the right place? 😅
I can add more detail if it is needed...

#### 22. Users Automatic Blocks
Automatically block users based on activities or suspicious data using customizable rules. 
![treshold_actions](https://github.com/user-attachments/assets/6138226b-e33e-4e15-838b-452e80853b40)
##### 1) Add Rules
Define how and when each rule applies:
- About user section is blank
- User has not created content
- Comments or about section contains links
- User email is not confirmed
- Email domain included in the list (can also act as an allow/block list)
![new_rule](https://github.com/user-attachments/assets/cfd5c2fe-6ae8-4680-8683-35c7d5546f52)
##### 2) Define the Threshold
Each rule contributes weight to the "spam risk index," and users who exceed the defined threshold can be blocked.
For example, if the threshold is set to "6" and each of the two defined rules has a weight of 5, both conditions must be met for a user to be flagged, as shown in the example screenshot.
##### 3) Possible Actions
- If "Perform users blocking" is unchecked: Calculates scores and generates a CSV with flagged users for review.
- If checked: Prompts for confirmation, blocks flagged users, and generates a CSV with blocked users.
##### Recommendation:
Review the CSV of flagged users before confirming to block them. However, blocked users can still be reviewed and unblocked later through Global Moderation > Blocked Users (/admin/moderated_users?blocked=true).

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

Successfully merging this pull request may close these issues.

3 participants