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 way to delete spam/unused users #8470

Open
rubenwardy opened this issue Dec 12, 2022 · 8 comments
Open

Add way to delete spam/unused users #8470

rubenwardy opened this issue Dec 12, 2022 · 8 comments
Labels
enhancement Adding or requesting a new feature. undecided These features might not be implemented. Can be prioritized by sponsorship.

Comments

@rubenwardy
Copy link

rubenwardy commented Dec 12, 2022

Describe the problem

My weblate instance has been targeted by a large number of spammy sign ups. Automated bots create accounts to link to their websites. Due to rel=ugc, this won't actually help their SEO. But it may be resulting in my website being seen as less trustworthy (I've been banned from Bing recently for some unknown reason), and having a large number of fake users is annoying

Describe the solution you'd like

There should be a way to delete spam/unused users. The criteria could be not a member of a project, never contributed to the project, and not used their account within a set period of recency

Describe alternatives you've considered

It would also be good to have better checks to prevent spammy sign ups.

Or perhaps a way to disable user profiles completely

Screenshots

No response

Additional context

My instance is at https://weblate.rubenwardy.com/

@rubenwardy
Copy link
Author

I've found REGISTRATION_CAPTCHA, this should definitely be enabled by default or highlighted in tutorials.

I've done UPDATE accounts_profile SET codesite='', website=''; to remove the URLs

@nijel
Copy link
Member

nijel commented Dec 14, 2022

REGISTRATION_CAPTCHA is enabled by default:

# Captcha for registrations
REGISTRATION_CAPTCHA = True

@github-actions
Copy link

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

@github-actions github-actions bot added the wontfix Nobody will work on this. label Dec 25, 2022
@rubenwardy
Copy link
Author

"A computer can never be held accountable, therefore a computer must never make a management decision"

@github-actions github-actions bot removed the wontfix Nobody will work on this. label Dec 26, 2022
@comradekingu
Copy link
Contributor

What accountability you have isn't helped by turning that off…?
You could add your instance to https://weblate.org/discover/ to help its discoverability :)

@nijel nijel added enhancement Adding or requesting a new feature. undecided These features might not be implemented. Can be prioritized by sponsorship. labels Jan 6, 2023
@github-actions
Copy link

github-actions bot commented Jan 6, 2023

This issue has been put aside. It is currently unclear if it will ever be implemented as it seems to cover too narrow of a use case or doesn't seem to fit into Weblate.

Please try to clarify the use case or consider proposing something more generic to make it useful to more users.

@rubenwardy
Copy link
Author

rubenwardy commented Nov 6, 2023

What accountability you have isn't helped by turning that off…? You could add your instance to weblate.org/discover to help its discoverability :)

I was commenting on the stale issue bot

I have REGISTRATION_CAPTCHA enabled but it doesn't seem to be that effective. My instance has 1370 registered users, but only a few of those are legitimate

@nijel
Copy link
Member

nijel commented Nov 29, 2023

The captcha implementation is pretty basic right now, see also #1462.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding or requesting a new feature. undecided These features might not be implemented. Can be prioritized by sponsorship.
Projects
None yet
Development

No branches or pull requests

3 participants