Skip to content

Spamming #3

Closed
mountain opened this Issue Sep 2, 2012 · 13 comments

8 participants

@mountain
mountain commented Sep 2, 2012

Right now the site are suffering with spamming!

@aaronblohowiak
Owner

I would like to keep the barrier to contributing very low if possible, so I don't want to make it hard for people to contribute -- not sure what the best way a) prevent spam and b) make it painless to contribute is. I have thought about using Github for auth.. what do you think?

@radius314

how about a captcha?

@frankamp

a captcha where the user must evaluate code! because machines are terrible at... oh. nevermind.

@aaronblohowiak
Owner
@mikemccabe

perhaps you could require that submitted code be syntax-error-free Lua?

@aaronblohowiak
Owner
@kmatt
kmatt commented Nov 10, 2012

Can the code be EVALed in a Redis instance as a check?

@jimktrains

What about something like AskiMet?

There is also https://github.com/achiu/rack-recaptcha that plugs into Rack and not rails.

@jimktrains

Also, perhaps tossing out any script that has HTML in it?

@aaronblohowiak
Owner
@aaronblohowiak
Owner
@aaronblohowiak
Owner

Thanks for the offers. It should be fine now. Please email me aaron.blohowiak@gmail.com if you notice any more spam. I've merged an PR that blocks '<a', '<p' and 'http:'. If you want to make it so github-authorized contributors are free from these checks, I will gladly merge the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.