Community
Participate
Working Groups
We have bug 442999 which can be used if someone *creates* a new spam bug. Unfortunately spammers detected that they can reuse old, valid bugs. Please provide a convenient way to report such users / delete spam comments. Recent span comments I'm aware of: - bug 35779 comment 276 by spammer omarandemad@gmail.com - bug 404776 comment 51 by spammer omarandemad@gmail.com - bug 388476 comment 136 by spammer mikehercus@yahoo.com I can think about tagging such comments as "spam" and to enable some kind of automated query for suspending users creating such comments? I've tagged the comments above already (but I can't suspend user accounts), here is the query: https://bugs.eclipse.org/bugs/buglist.cgi?f1=comment_tag&list_id=18846991&o1=equals&query_format=advanced&v1=spam
I've cleaned up the identified comments, and as an experiment have granted you permission to edit users which should allow you to suspend these kinds of abusers in future. If that works out, we can look into giving a broader group of committers that same permission, in order to allow the community to 'police' these things. I know that bugzilla is working on providing users with a way to edit their own comments, but I'm not sure if that will also result in a permission to allow other people to edit them. For now it requires direct interaction with bugzillas data which is restricted to the webmaster team. As such for the foreseeable future I think that the way to handle these things will be to use something similar to bug 442999. To that end I've filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=549490 so that the community can flag comments that need to be removed. -M.
(In reply to Eclipse Webmaster from comment #1) > I've cleaned up the identified comments, and as an experiment have granted > you permission to edit users which should allow you to suspend these kinds > of abusers in future. On the user page, which "bit" need to be set to "suspend" the user? Is this "Bugmail disabled"? Or how you deal with spammers? Just "Delete"? > If that works out, we can look into giving a broader > group of committers that same permission, in order to allow the community to > 'police' these things. I personally would prefer a smaller subset of this administration page, because I do not want have all this rights to manage users, also for security reasons. One button + text field would be enough "Suspend user" + "Reason why". > I know that bugzilla is working on providing users with a way to edit their > own comments, but I'm not sure if that will also result in a permission to > allow other people to edit them. For now it requires direct interaction > with bugzillas data which is restricted to the webmaster team. > > As such for the foreseeable future I think that the way to handle these > things will be to use something similar to bug 442999. To that end I've > filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=549490 so that the > community can flag comments that need to be removed. OK, thanks, understood.
(In reply to Andrey Loskutov from comment #2) > (In reply to Eclipse Webmaster from comment #1) > > I've cleaned up the identified comments, and as an experiment have granted > > you permission to edit users which should allow you to suspend these kinds > > of abusers in future. > > On the user page, which "bit" need to be set to "suspend" the user? Is this > "Bugmail disabled"? Or how you deal with spammers? Just "Delete"? https://bugs.eclipse.org/bugs/editusers.cgi Find the user, then save something in the Disable text: field. We typically simply write "Spam".
(In reply to Eclipse Webmaster from comment #1) > I've cleaned up the identified comments Unfortunately, the subsequent comments have been renumbered, such that there are no "missing" comment numbers... which breaks the anchor references. As a quick (and fortunately harmless, so far) example, see the current end of Bug 388476, where originally 136 was spam and 137 and 138 was discussing the spam (and linking to 136). But now that the spam is gone, 137 and 138 are shuffled down and renumbered, such that 136 is complaining about "136" and 137 is replying to "137". Fortunately there are no further comments or it would get more confusing.
This issue has been migrated to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/435.
