Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spam spam spam spam #33

Closed
carols10cents opened this issue Mar 13, 2014 · 3 comments · Fixed by #44
Closed

Spam spam spam spam #33

carols10cents opened this issue Mar 13, 2014 · 3 comments · Fixed by #44
Labels

Comments

@carols10cents
Copy link
Collaborator

This is a form on the internet... so I predict it'll be like, 4 hours after tweetings til we start getting spam :(

Ask people to type 'SCRC' into a text field and reject with a human readable error message if it's not that?

This can wait til after we open, buuuuut i waaaarrrned yooou

@carols10cents
Copy link
Collaborator Author

monty_python_spam

@jnf
Copy link
Owner

jnf commented Mar 13, 2014

I've done this thing in the past where I make an input like:

<input type='text' name='email_for_reals' value='Enter your email address' />

And then in the stylesheet I get all like:

input[name=email_for_reals] { display: none; }

THEN, in the controller, I kick out any post where email_for_reals isn't the default value. Robots will always mess with an email field, and don't know/care/understand that css makes it invisible. It's a neat solution, until someone with a screen reader wonders why their infos never save :(

@ninjapanzer
Copy link
Collaborator

if you submit the CSRF as a hidden field in the for that does a great job

@jnf jnf mentioned this issue Mar 14, 2014
@jnf jnf closed this as completed in #44 Mar 14, 2014
jnf added a commit that referenced this issue Mar 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants