SPAM on trac from github users

52 views
Skip to first unread message

Frédéric Chapoton

unread,
Aug 1, 2019, 7:45:28 AM8/1/19
to sage-devel
Hello,

The user gh-mohdazher has just open a spam-ticket on trac. I have nuked this ticket.

This is the second time in one month that we observe spamming behaviour from github users.

* How to avoid that ?

* Can we blacklist eternally these guys ? Who has the power to do that ?

Frederic

Dima Pasechnik

unread,
Aug 1, 2019, 8:25:08 AM8/1/19
to sage-devel, sagemath-admins
On Thu, Aug 1, 2019 at 2:45 PM Frédéric Chapoton <fchap...@gmail.com> wrote:
> The user gh-mohdazher has just open a spam-ticket on trac. I have nuked this ticket.
>
> This is the second time in one month that we observe spamming behaviour from github users.
>
> * How to avoid that ?

In the previous case it was possible to report the user to GitHub, as
it was an obvious violation of GitHub's no-spamming.
Here the user in question does nor have anything public on GitHub to
complain about, except
the now gone (?) trac ticket. Still, I hope it is possible to use that
contents to report the user to GitHub.



>
> * Can we blacklist eternally these guys ? Who has the power to do that ?
>
> Frederic
>
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/0e8ce233-02a5-4214-820b-95095a00112d%40googlegroups.com.

E. Madison Bray

unread,
Aug 2, 2019, 5:20:04 AM8/2/19
to sage-devel
On Thu, Aug 1, 2019 at 1:45 PM Frédéric Chapoton <fchap...@gmail.com> wrote:
>
> Hello,
>
> The user gh-mohdazher has just open a spam-ticket on trac. I have nuked this ticket.
>
> This is the second time in one month that we observe spamming behaviour from github users.
>
> * How to avoid that ?

You don't. If you want to run a service where people are given access
to post content you're going to have occasional spammers no matter
what, without completely locking things down as was the case
previously.

By allowing GitHub users to log in we are pushing spam prevention on
to GitHub which does a lot more in the first place than we can do
alone.

Even if the project were moved to GitHub, or GitLab, a large-enough
project will attract some spam. CPython has been getting spam PRs
sometimes, for example. Just have to accept it, up to a point where
it becomes unmanageable at least.
Reply all
Reply to author
Forward
0 new messages