reCAPTCHA is accepting random values - laravel-4

I'm using Greg Gilbert's reCAPTCHA validator for Laravel 4 (https://github.com/greggilbert/recaptcha).
I know that reCAPTCHA only needs one word on two to validate forms but my problem is different. I actually have a single word displayed on my reCAPTCHA, the second one is missing. And unfortunately, the displayed word is the "pictured-word", you know, the word for which you can write whatever you like and it will be accepted.
So if it shows number 109, I can write "108" and my form will be accepted.
How to fix that please ?

After some tests, I've found that if I use Firefox's "Private navigation" window, my reCAPTCHA is displaying 2 words instead of 1 as I described here.
It means that if you are connected to your Google account on your web browser, reCAPTCHA "trusts" you a little bit more than a not-connected user and shows you only one word/number.

Related

How to get only numeric text in recaptcha?

In my site its very difficult in some cases that the given text images in Recaptcha are not clear. This lead to reduce the intreset of login into our site. I needs some help on getting only numeric values in recaptcha.
No, this is not possible. Recaptcha has been designed to avoid any OCR's and automated bot attacks.

"facebook comment id" added to url - inconveniently

A user comments on the page, the comment is posted to their facebook wall. When another facebook user clicks the link to see the comment it links back to the page but with a massive string of numbers on the end.
http://canofclouds.com/thought/?fb_comment_id=fbc_10150505683457013_20914817_10150507783662013#55
The original url was: http://www.canofclouds.com/thought/#55
This is all fine so far though, until the user clicks a button to go to
http://www.canofclouds.com/thought/#56
Instead, it goes to:
http://canofclouds.com/thought/?fb_comment_id=fbc_10150505683457013_20914817_10150507783662013#f25e670a6c
Which is not good - because it doesn't exist. Ideally it would just go to http://www.canofclouds.com/thought/#56
Normally, when the user clicks the next button a flurry of javascript grabs the hash key (in this case #55) then adds 1 to it (to make #56 - yay) and executes an ajax call to grab the new content. This facebook stuff is making things a little complicated though.
Any ideas?
Edit: Even more ideally i could disable the 'fb comments id' altogether.
You shouldn't use hash keys to link to your page. You should use a canonical URL to do so.
There are a few questions here on stack overflow about how to deal with this.
The only way around it if you choose not to make canonical urls, is to do URL Rewriting at the network or web server level.

W3 Validation errors

I am validating against html5 and I know that the validator is not 100% but it even shows it should allow this in it's suggestion...
Ouptut:
Line 75, Column 92: Bad value home for attribute rel on element a:
Keyword home is not registered.
…bomb/" rel="home" title="beefbomb.com"><img src="http://localhost/local_folder…
It then tells me to take a look at the microformats wiki... http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions
Which defines:
Keyword: home
Effect on a, area: Hyperlink
Brief description: …indicates that the [referenced document] is
the homepage of the site in which the current page appears. can be
combined with 'alternate' to indicate for example a feed for the site
of the current page.
Link to specification: rel-home
Why could this be?
Microformats aren't part of the official spec. A future ua could come along that decides to treat links with rel="home" on them as links to go to the homescreen of the device for instance, without going against the spec.
The warning is to ask you, "Have you done this for a reason, or by mistake?". If you know what you are doing and why, it's fine. If you decided to make up a new rel attribute for your own reasons, you get told that it's not in spec, but that a system already exists that uses it.

Looking for an anti-spam solution easier to implement than Captcha

I'm looking for a simple anti spam form submission solution, other than Captcha. I've tried implementing Captcha into my website for anti-spam purposes, but it's been too difficult to integrate into the site. I don't get many spam attacks but I'd like to have something in place for the random spam that I get. Does anyone know of something they think would work?
you can add an additional textfield to your form and hide it with css. human users don't see the field, so it should always be empty. spambots usually fill out all form fields and don't know that this one is hidden. if you receive any content in this field, reject the form submission.
Put up something like "What is 3 plus 6?" and give the user a form to type the answer. Any human will get that, including blind ones who can't see a captcha, but no bot will. You don't even need to vary the numbers, really.

UI - How I can make users effectively read what my program says?

I have a simple form that searches through the 2000+ issues of a 3rd party webcomic. (Easy, it's like xkcd: http://url/number
That form is as easy as possible, is like this:
What number do you want?
User writes a number, clicks ok, and goes on the 3rd party website on a new tab
Then, my form asks a question: "Did you find that issue memorable? Enter the name here, and we will add it to the "best issues" in home page"
When the user will write the name of the issue, it is added to the database (pending moderation by me)
So, I supposed this design is the easiest and convenient that users can find.
Unfortunately, NONE of the users (maybe a 2% behaved correctly) will actually read what I asked. Some of the issues are offline, and gives a 404. On that issues users will write in the textbox a completely wrong title, and correctly capitalized!
It's like if i would name http://xkcd.com/627/ as "The Great Adventures of Jack Smith"
Users are from around all over the country, with different browsers, and have a different cookie.
I cannot believe that my users will not read what I ask, it is a WHITE PAGE with a button that disappears when clicked and a textbox.... easier than that???
Maybe i should put a checkbox with "I acknowledge that this form is for submitting memorable issues, not for fun"? Oh, who will read that?
Or maybe i could enable the textbox only if the user has effectively clicked the link?
Do your users understand your site/service?
I, for one, don't remember (web-)comics by their issue number, but by their content. When asked what xkcd comic number I would like to see, I'd probably input random numbers like 42, 123 or 666 or something.
After you make me guess for a number you ask me if the associated comic is particularly epic, then you ask me to do some data entry for it to put it on some kind of hall of fame. Honestly I do not understand what the logic is behind inserting titles for non existing comics -- are you sure they don't actually land them on the comic page for "The Great Adventures of Jack Smith"? The 2% of your userbase probably noticed the issue in the URL you generated for them, addressed it and typed in the right title. Or, maybe, they are typing the name of the comic they actually wanted to see instead.
There's a simple way to know. Have your mom use it and do not correct her if she makes mistakes. All mistakes she makes are your fault, not hers.
Without having the text of the labels you have put it's harder for us to second guess what's going wrong than it is for you.
Try it!!
You could try parsing the title of the page and obtaining the title yourself
OR you might want to request the username/handle.
Once the user enters the details and clicks SUBMIT, Show a confirmation page ( preview of how the submission will be listed). Make sure to include the username/handle as the person who submitted it (This brings a sense of responsibility to the guy who submits). Remember to keep a back button to allow the user to go back and make the necessary changes ans submit again.
Allow users to create profiles on ur site (they maybe as simple as stackoverflow's profile system. here's mine for example). Unless he is logged-in, submissions posted as anonyomous. Rest same as above.
NOTE: There might be a slim possibility that, U are be being targetted by spam / captcha bots. Hence the random text entries. still. do implement the above. A better UI never hurt anyone. Right??...

Resources