[spam report] in review comments by compromised user thekorn
User: https:/
Review: https:/
And: https:/
One or more of this guys email accounts is compromised. I received loads of direct spam from him a while ago, but he never responded when I e-mailed him about it.
I've tried multiple times to get this junk cleared up, including resurrecting the last question a couple of times.
https:/
https:/
https:/
https:/
Every time the question expires with no action. How many times should I ask? If you can't keep up, then give project maintainers the ability to at least flag and hide spam (i.e. implement the now 12 year old https:/
Question information
- Language:
- English Edit question
- Status:
- Open
- Assignee:
- Colin Watson Edit question
- Last query:
- 2018-04-21
- Last reply:
| Colin Watson (cjwatson) said : | #1 |
I'm sorry that we haven't communicated well on this one.
The core problem here is not really with reporting mechanisms; it's that we don't currently have a good way to deal with this particular type of spam (which is comparatively rare in Launchpad), short of manual database surgery which we try very hard to avoid. I've been spending some of my spare time working on this over the last week or so, and have been making good progress, of which this is the first part (I'm not expecting you to review it, just citing it for transparency):
https:/
The second part of this will be a fix for bug 1680746. I have this working in a local instance, and am just sorting out tests and generally polishing it up before submitting it for code review.
Once these two chunks of work have landed, we'll be able to remove this spam easily, and in general we'll be able to respond to this particular type of spam more quickly in future.
Can you help with this problem?
Provide an answer of your own, or ask Stephen Boddy for more information if necessary.
