Codea Spam Reporter is a nifty little program by @SkyTheCoder and myself that checks for spammers on the forums and reports them to the Spammer discussion.
(@SkyTheCoder did most of the work, i’m working on the reporting and other minor things, as well as the dependency version)
The links below will be updated as it is improved:
<a href=http://codea.housercompany.com/alpha/index.php?v=934>Original Code
<a href=http://codea.housercompany.com/alpha/index.php?v=933>Dependency Version
@Prynok, the reason @SkyTheCoder is being reported constantly is that the reporter was still a little buggy and he posted a spam template for testing purposes. I believe i have fixed the bug and so it shouldn’t happen again.
finally, I am what I expected @jakAttak
@SkyTheCoder I have uploaded a new version which does what you wanted (Links to the spammer profile but doesn’t use the @Username so that they aren’t alerted)
@Prynok, I did like your suggestion about a list of “trusted” people who won’t be reported, and the latest version (see first post) has this feature.
I hope none of you are spammers in hiding >:)
If you guys think of anything that the spammers often say that should be added to the list of things to check for, please let me know
They tend to say “our” if they work for a group
@CodeaNoob, true but that is also something that is said often by people who are not spamming.
@JakAttak “Check out this website:”
Just about all possible forms of “Check out this website” are already checked for
“Follow me on”
“Buy this” or “Try this out”
Good ideas. Will work these in soon
I was going to post the discussion…
Nice job, though.
@SkyTheCoder At least he gave credit!
I was thinking about this, and I realized that it’s only useful if people constantly go back and run it. This seemed like it might be a barrier to spam getting reported and so I came up with a partial solution.
I’ve just finished turning (most of) this into a class. What I’ve done is create a project that takes the checking and reporting parts of the Spam Reporter and put them in a class. Then, it calls that class. Basically, if you add this as a dependency to any of your projects, they will check for and report spam every time you run them. All behind the scenes.
This should maximize the reporting of spam.
I have tested it and it worked for me, but please let me know if you run into any issues.
(Download the code into a project, and add that project as a dependency to any projects you run often)