Here is my thoughts on this :
Implement community moderation: Allow the community of users on pagure.io to help moderate and flag spam projects and users. This could be done through a reporting system or through user-driven flagging mechanisms that alert administrators to potentially problematic projects.
Increase the frequency of automated clean-up scripts: Increasing the frequency of these scripts could help keep the site cleaner and reduce the need for manual intervention by administrators.
Increase the frequency of automated clean-up scripts: Increasing the frequency of these scripts could help keep the site cleaner and reduce the need for manual intervention by administrators.
On Wed, Apr 26, 2023 at 8:38 AM Michal Konecny <mkonecny@xxxxxxxxxx> wrote:
Regarding the #3, how do you find spam projects now? Could the script do
the same?
Michal
On 25. 04. 23 23:17, Kevin Fenzi wrote:
> Hey folks.
>
> So, a few weeks back I noticed some spam projects on pagure.io.
> So, I cleaned up about 165 of them and deactivated 165 spam users.
>
> Now, I see there's another pile of them. :(
>
> So, I started to look at cleaning things up again, but I think we need a
> better solution that doesn't involve admins manually cleaning things up.
> ;( Additionally, the clean up is not really very scripted and takes a
> long time to do.
>
> So, thoughts on a longer term solution? I can think of a few:
>
> 1. only allow fedora 'contributors' to make new projects. (ie, people in
> at least one non cla/non base ipa group
> Pros:
> - Would very likely cut off the spam or at least cut it way down.
> - Might be easy to implement? (not sure tho!)
> Cons:
> - Would block legit people who aren't fedora contributors.
>
> 2 Some kind of moderation for new projects
> Pros:
> - Would let non fedora folks make new projects.
> - Would likely cut spam
> Cons:
> - Would require someone to moderate things
> - Would requite us to make some kind of moderation code
>
> 3. A script to do all the cleanup so we could do it easier and some kind
> of 'bad words' blocklist we could put in place to stop obvious spammers
> (most of these are bogus "exam answers" ones)
> Pros:
> - Will cut down on spam some, but not fully.
> Cons:
> - Will have to write the script and implement the blocklist
> - It's likely spammers will use different words over time and avoid the
> block.
>
> Or perhaps someone has further clever ideas? Happy to hear em. ;)
>
> kevin
>
> _______________________________________________
> infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
