I agree with P JH. One of my websites, which gets a considerable amount of visit is being hit by spam recently. My plan to tackle this is to implement multiple captchas for the registration and feedback forms, along with reCaptcha. However, I am not ready to let go of reCaptcha because it has been very useful and easy to integrate. Even then, it cannot stop people who manually and delibrately spread spam around. -- Kaustav Das Modak --------------------------------------------------------------------------- ------ Launchpad: https://launchpad.net/~kaustav-dasmodak<https://launchpad.net/%7Ekaustav-dasmodak> Facebook: http://www.facebook.com/kaustav.dasmodak * Kill software piracy. Switch to free and open source software.*
On 17 January 2011 14:01, P JH <pauljherr...@gmail.com> wrote:
> On Mon, Jan 17, 2011 at 2:59 AM, Modern Jess <modernve...@gmail.com>wrote:
>> I've had to resort to other means
> To every one complaining about this - you do realise that you can't expect > just one technology to stop spammers - reCAPTCHA should be *one* of the > things you use to stop spammers, not the *only* thing.
> -- > PJH
> -- > You received this message because you are subscribed to the Google Groups > "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to > recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > For more options, visit this group at > http://groups.google.com/group/recaptcha?hl=en.
PJH - your SPAM defense is only as good as your weakest link.
Perhaps instead of ignoring the issue, Google should respond with some
feedback ... it doesn't have to be a answer or a even fix, but just a
simple reply would help in this regard.
Customers should be alerted if this product/system has been
compromised.
On Jan 17, 3:31 am, P JH <pauljherr...@gmail.com> wrote:
> On Mon, Jan 17, 2011 at 2:59 AM, Modern Jess <modernve...@gmail.com> wrote:
> > I've had to resort to other means
> To every one complaining about this - you do realise that you can't expect
> just one technology to stop spammers - reCAPTCHA should be *one* of the
> things you use to stop spammers, not the *only* thing.
Has anyone, by chance, looked for an email contact at Google to see if we can reach a support person / team for reCAPTCHA? A very simple, nice and professional email could do ALOT to getting our requests reviewed and replied to?!
On Tue, Jan 18, 2011 at 5:06 PM, Nick Wilcox <wilc...@gmail.com> wrote:
> PJH - your SPAM defense is only as good as your weakest link.
With all due respect - rubbish.
The "weakest link" analogy only applies if you're running such things in parallel and accepting *any* "yes" answer rather than requiring all of them to say "yes." Other things you can use in addition to reCAPTCHA (not all may be applicable to particular applications, and some not worth the effort required to implement them):
1) Akismet 2) IP blacklists 3) New user moderation 4) Peer moderation 5) Token authentication to verify account activation 6) Bayesian filtering 7) Markovian discrimination
> Perhaps instead of ignoring the issue, Google should respond with some > feedback ... it doesn't have to be a answer or a even fix, but just a > simple reply would help in this regard.
Perhaps, instead of railing on a user list when it's obvious there's no-one answering from the supplier, those with concerns could email support directly[1] instead of incessantly moaning on here that their one no-cost barrier to spam isn't working as effectively as it could, and defending their decision to use only one method of stopping spammers.
> Customers should be alerted if this product/system has been > compromised.
> On Jan 17, 3:31 am, P JH <pauljherr...@gmail.com> wrote: >> On Mon, Jan 17, 2011 at 2:59 AM, Modern Jess <modernve...@gmail.com> wrote: >> > I've had to resort to other means
>> To every one complaining about this - you do realise that you can't expect >> just one technology to stop spammers - reCAPTCHA should be *one* of the >> things you use to stop spammers, not the *only* thing.
>> -- >> PJH
> -- > You received this message because you are subscribed to the Google Groups "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to recaptcha+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.
> On Mon, Jan 17, 2011 at 2:59 AM, Modern Jess <modernve...@gmail.com> wrote:
> > I've had to resort to other means
> To every one complaining about this - you do realise that you can't expect
> just one technology to stop spammers - reCAPTCHA should be *one* of the
> things you use to stop spammers, not the *only* thing.
On Tue, Jan 18, 2011 at 5:26 PM, craiggers <cko...@gmail.com> wrote: > That's great. Why don't you share some of the others with us.
> Craig
> On Jan 17, 3:31 am, P JH <pauljherr...@gmail.com> wrote: >> On Mon, Jan 17, 2011 at 2:59 AM, Modern Jess <modernve...@gmail.com> wrote: >> > I've had to resort to other means
>> To every one complaining about this - you do realise that you can't expect >> just one technology to stop spammers - reCAPTCHA should be *one* of the >> things you use to stop spammers, not the *only* thing.
>> -- >> PJH
> -- > You received this message because you are subscribed to the Google Groups "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to recaptcha+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.
> instead of incessantly moaning on here that their
> one no-cost barrier to spam isn't working as effectively as it could,
> and defending their decision to use only one method of stopping
> spammers.
I initially posted to determine if it was just me, since there was
very little recent mention of reCAPTCHA being broken anywhere I
looked. I wanted to make mention of it since nobody else was.
I *did* take additional countermeasures as soon as reCAPTCHA fell.
They're working fairly well at the moment, although the IP blacklist
portion of my countermeasures are ensnaring some folks who are unlucky
enough to be served by an ISP that uses a small bank of IP proxies
(like AOL). So be it.
But moaning? No. Discussing the current situation with other people
who may or may not be having the same problem, yes. I don't expect
Google to read this or respond. My post was directed at others who
might be having the same problem.
You sir are an ass of the first order. Unfortunately the internet is
littered with asses just like yourself who style themselves as
internet know-it-alls and who sit all day behind keyboards making
grand pronouncements from on-high. With all due respect (which is to
say *none*) you can go run up a big fat weed.
On Wed, Jan 19, 2011 at 10:59 PM, Modern Jess <modernve...@gmail.com> wrote: >> instead of incessantly moaning on here that their >> one no-cost barrier to spam isn't working as effectively as it could, >> and defending their decision to use only one method of stopping >> spammers.
> I initially posted to determine if it was just me,
A few days ago, I described some problems I seem to have with ReCaptcha. These problems have not been solved yet. In summary:
On my guestbook (http://www.yawp.nl/guestbook) I get a could not open socket & connection timed out error whenever I fill in some info. I tried a couple of possible solutions I found searching in Google. Funny enough everything goes smoothly on my develop server. So I tried to get different keys for the develop server and the live server, but it made no difference. So I came to the conclusion it must be the live server's config.
But now I found that spammers somehow seemed to get passed, and filled my guestbook. This makes me wonder. Apparently it seems they can actually surpass the entire ReCaptcha protection. This brings about a whole new aspect...
On Thu, Jan 20, 2011 at 17:02, Herry <he...@redcirclemedia.nl> wrote: > Trying to get passed the bitchfight
> A few days ago, I described some problems I seem to have with ReCaptcha. > These problems have not been solved yet. In summary:
> On my guestbook (http://www.yawp.nl/guestbook) I get a could not open socket > & connection timed out error whenever I fill in some info. > I tried a couple of possible solutions I found searching in Google. > Funny enough everything goes smoothly on my develop server. So I tried to > get different keys for the develop server and the live server, but it made > no difference. So I came to the conclusion it must be the live server's > config.
> But now I found that spammers somehow seemed to get passed, and filled my > guestbook. This makes me wonder. Apparently it seems they can actually > surpass the entire ReCaptcha protection. This brings about a whole new > aspect...
> -- > You received this message because you are subscribed to the Google Groups > "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to > recaptcha+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/recaptcha?hl=en.
Can't add much more than adrian did above. It is a firewall
configuration issue that is causing your socket error. You say your
problem have not been solved yet, however, that very problem has been
solved in this group over and over again (which is why it gets so damn
old). Search the group for "socket error".
You don't need separate keys for a localhost vs. production
implementation. I'm guessing your local machine is on a different
network than your production machine. You need to contact the hosting
company of your production machine and ask them to open some ports
(search for "socket error" to find out more).
As for the spam getting through, quite frankly, I am not having that
problem with my implementations, so I'm not sure why so many are
claiming the issue.
This bitch is out...back to being a self-styled internet guru.
On Jan 20, 7:02 pm, Herry <he...@redcirclemedia.nl> wrote:
> A few days ago, I described some problems I seem to have with ReCaptcha.
> These problems have not been solved yet. In summary:
> On my guestbook (http://www.yawp.nl/guestbook) I get a could not open
> socket & connection timed out error whenever I fill in some info.
> I tried a couple of possible solutions I found searching in Google.
> Funny enough everything goes smoothly on my develop server. So I tried
> to get different keys for the develop server and the live server, but it
> made no difference. So I came to the conclusion it must be the live
> server's config.
> But now I found that spammers somehow seemed to get passed, and filled
> my guestbook. This makes me wonder. Apparently it seems they can
> actually surpass the entire ReCaptcha protection. This brings about a
> whole new aspect...
> Can't add much more than adrian did above. It is a firewall > configuration issue that is causing your socket error. You say your > problem have not been solved yet, however, that very problem has been > solved in this group over and over again (which is why it gets so damn > old). Search the group for "socket error".
> You don't need separate keys for a localhost vs. production > implementation. I'm guessing your local machine is on a different > network than your production machine. You need to contact the hosting > company of your production machine and ask them to open some ports > (search for "socket error" to find out more).
> As for the spam getting through, quite frankly, I am not having that > problem with my implementations, so I'm not sure why so many are > claiming the issue.
> This bitch is out...back to being a self-styled internet guru.
> On Jan 20, 7:02 pm, Herry <he...@redcirclemedia.nl> wrote: > > Trying to get passed the bitchfight
> > A few days ago, I described some problems I seem to have with ReCaptcha. > > These problems have not been solved yet. In summary:
> > On my guestbook (http://www.yawp.nl/guestbook) I get a could not open > > socket & connection timed out error whenever I fill in some info. > > I tried a couple of possible solutions I found searching in Google. > > Funny enough everything goes smoothly on my develop server. So I tried > > to get different keys for the develop server and the live server, but it > > made no difference. So I came to the conclusion it must be the live > > server's config.
> > But now I found that spammers somehow seemed to get passed, and filled > > my guestbook. This makes me wonder. Apparently it seems they can > > actually surpass the entire ReCaptcha protection. This brings about a > > whole new aspect...
> -- > You received this message because you are subscribed to the Google Groups > "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to > recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > For more options, visit this group at > http://groups.google.com/group/recaptcha?hl=en.
That's probably true and I'm quite sure the team is on it (even though there's no announcement here). I saw an update on recaptcha images lately (instead of full black text, only black outline is visible).
On Fri, Jan 21, 2011 at 14:18, mono...@gmx.net <mono...@gmx.net> wrote: > i have the same problem with phpbb for some time so i think its definitely > cracked.
> changed to phpbbs own gd captcha now and spam is stopped.
> maybe your site was just not visited by bots yet...
>> Can't add much more than adrian did above. It is a firewall >> configuration issue that is causing your socket error. You say your >> problem have not been solved yet, however, that very problem has been >> solved in this group over and over again (which is why it gets so damn >> old). Search the group for "socket error".
>> You don't need separate keys for a localhost vs. production >> implementation. I'm guessing your local machine is on a different >> network than your production machine. You need to contact the hosting >> company of your production machine and ask them to open some ports >> (search for "socket error" to find out more).
>> As for the spam getting through, quite frankly, I am not having that >> problem with my implementations, so I'm not sure why so many are >> claiming the issue.
>> This bitch is out...back to being a self-styled internet guru.
>> On Jan 20, 7:02 pm, Herry <he...@redcirclemedia.nl> wrote: >> > Trying to get passed the bitchfight
>> > A few days ago, I described some problems I seem to have with ReCaptcha. >> > These problems have not been solved yet. In summary:
>> > On my guestbook (http://www.yawp.nl/guestbook) I get a could not open >> > socket & connection timed out error whenever I fill in some info. >> > I tried a couple of possible solutions I found searching in Google. >> > Funny enough everything goes smoothly on my develop server. So I tried >> > to get different keys for the develop server and the live server, but it >> > made no difference. So I came to the conclusion it must be the live >> > server's config.
>> > But now I found that spammers somehow seemed to get passed, and filled >> > my guestbook. This makes me wonder. Apparently it seems they can >> > actually surpass the entire ReCaptcha protection. This brings about a >> > whole new aspect...
>> -- >> You received this message because you are subscribed to the Google Groups >> "reCAPTCHA" group. >> To post to this group, send email to recaptcha@googlegroups.com. >> To unsubscribe from this group, send email to >> recaptcha+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/recaptcha?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to > recaptcha+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/recaptcha?hl=en.
> That's probably true and I'm quite sure the team is on it (even though > there's no announcement here). I saw an update on recaptcha images > lately (instead of full black text, only black outline is visible).
> On Fri, Jan 21, 2011 at 14:18, mono...@gmx.net <mono...@gmx.net> wrote: > > i have the same problem with phpbb for some time so i think its > definitely > > cracked.
> > changed to phpbbs own gd captcha now and spam is stopped.
> > maybe your site was just not visited by bots yet...
> > -- > > Mit freundlichen Grüssen > > André Bauer
> >> Can't add much more than adrian did above. It is a firewall > >> configuration issue that is causing your socket error. You say your > >> problem have not been solved yet, however, that very problem has been > >> solved in this group over and over again (which is why it gets so damn > >> old). Search the group for "socket error".
> >> You don't need separate keys for a localhost vs. production > >> implementation. I'm guessing your local machine is on a different > >> network than your production machine. You need to contact the hosting > >> company of your production machine and ask them to open some ports > >> (search for "socket error" to find out more).
> >> As for the spam getting through, quite frankly, I am not having that > >> problem with my implementations, so I'm not sure why so many are > >> claiming the issue.
> >> This bitch is out...back to being a self-styled internet guru.
> >> On Jan 20, 7:02 pm, Herry <he...@redcirclemedia.nl> wrote: > >> > Trying to get passed the bitchfight
> >> > A few days ago, I described some problems I seem to have with > ReCaptcha. > >> > These problems have not been solved yet. In summary:
> >> > On my guestbook (http://www.yawp.nl/guestbook) I get a could not open > >> > socket & connection timed out error whenever I fill in some info. > >> > I tried a couple of possible solutions I found searching in Google. > >> > Funny enough everything goes smoothly on my develop server. So I tried > >> > to get different keys for the develop server and the live server, but > it > >> > made no difference. So I came to the conclusion it must be the live > >> > server's config.
> >> > But now I found that spammers somehow seemed to get passed, and filled > >> > my guestbook. This makes me wonder. Apparently it seems they can > >> > actually surpass the entire ReCaptcha protection. This brings about a > >> > whole new aspect...
> >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "reCAPTCHA" group. > >> To post to this group, send email to recaptcha@googlegroups.com. > >> To unsubscribe from this group, send email to > >> recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > >> For more options, visit this group at > >> http://groups.google.com/group/recaptcha?hl=en.
> > -- > > You received this message because you are subscribed to the Google Groups > > "reCAPTCHA" group. > > To post to this group, send email to recaptcha@googlegroups.com. > > To unsubscribe from this group, send email to > > recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > > For more options, visit this group at > > http://groups.google.com/group/recaptcha?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to > recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > For more options, visit this group at > http://groups.google.com/group/recaptcha?hl=en.
> 2011/1/21 Adrian Godong <adrian.god...@gmail.com>
>> That's probably true and I'm quite sure the team is on it (even though >> there's no announcement here). I saw an update on recaptcha images >> lately (instead of full black text, only black outline is visible).
>> On Fri, Jan 21, 2011 at 14:18, mono...@gmx.net <mono...@gmx.net> wrote: >> > i have the same problem with phpbb for some time so i think its >> > definitely >> > cracked.
>> > changed to phpbbs own gd captcha now and spam is stopped.
>> > maybe your site was just not visited by bots yet...
>> > -- >> > Mit freundlichen Grüssen >> > André Bauer
>> >> Can't add much more than adrian did above. It is a firewall >> >> configuration issue that is causing your socket error. You say your >> >> problem have not been solved yet, however, that very problem has been >> >> solved in this group over and over again (which is why it gets so damn >> >> old). Search the group for "socket error".
>> >> You don't need separate keys for a localhost vs. production >> >> implementation. I'm guessing your local machine is on a different >> >> network than your production machine. You need to contact the hosting >> >> company of your production machine and ask them to open some ports >> >> (search for "socket error" to find out more).
>> >> As for the spam getting through, quite frankly, I am not having that >> >> problem with my implementations, so I'm not sure why so many are >> >> claiming the issue.
>> >> This bitch is out...back to being a self-styled internet guru.
>> >> On Jan 20, 7:02 pm, Herry <he...@redcirclemedia.nl> wrote: >> >> > Trying to get passed the bitchfight
>> >> > A few days ago, I described some problems I seem to have with >> >> > ReCaptcha. >> >> > These problems have not been solved yet. In summary:
>> >> > On my guestbook (http://www.yawp.nl/guestbook) I get a could not open >> >> > socket & connection timed out error whenever I fill in some info. >> >> > I tried a couple of possible solutions I found searching in Google. >> >> > Funny enough everything goes smoothly on my develop server. So I >> >> > tried >> >> > to get different keys for the develop server and the live server, but >> >> > it >> >> > made no difference. So I came to the conclusion it must be the live >> >> > server's config.
>> >> > But now I found that spammers somehow seemed to get passed, and >> >> > filled >> >> > my guestbook. This makes me wonder. Apparently it seems they can >> >> > actually surpass the entire ReCaptcha protection. This brings about a >> >> > whole new aspect...
>> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "reCAPTCHA" group. >> >> To post to this group, send email to recaptcha@googlegroups.com. >> >> To unsubscribe from this group, send email to >> >> recaptcha+unsubscribe@googlegroups.com. >> >> For more options, visit this group at >> >> http://groups.google.com/group/recaptcha?hl=en.
>> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "reCAPTCHA" group. >> > To post to this group, send email to recaptcha@googlegroups.com. >> > To unsubscribe from this group, send email to >> > recaptcha+unsubscribe@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/recaptcha?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "reCAPTCHA" group. >> To post to this group, send email to recaptcha@googlegroups.com. >> To unsubscribe from this group, send email to >> recaptcha+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/recaptcha?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to > recaptcha+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/recaptcha?hl=en.
> > -- > > Mit freundlichen Grüssen > > André Bauer
> > 2011/1/21 Adrian Godong <adrian.god...@gmail.com>
> >> That's probably true and I'm quite sure the team is on it (even though > >> there's no announcement here). I saw an update on recaptcha images > >> lately (instead of full black text, only black outline is visible).
> >> On Fri, Jan 21, 2011 at 14:18, mono...@gmx.net <mono...@gmx.net> wrote: > >> > i have the same problem with phpbb for some time so i think its > >> > definitely > >> > cracked.
> >> > changed to phpbbs own gd captcha now and spam is stopped.
> >> > maybe your site was just not visited by bots yet...
> >> > -- > >> > Mit freundlichen Grüssen > >> > André Bauer
> >> >> Can't add much more than adrian did above. It is a firewall > >> >> configuration issue that is causing your socket error. You say your > >> >> problem have not been solved yet, however, that very problem has been > >> >> solved in this group over and over again (which is why it gets so > damn > >> >> old). Search the group for "socket error".
> >> >> You don't need separate keys for a localhost vs. production > >> >> implementation. I'm guessing your local machine is on a different > >> >> network than your production machine. You need to contact the > hosting > >> >> company of your production machine and ask them to open some ports > >> >> (search for "socket error" to find out more).
> >> >> As for the spam getting through, quite frankly, I am not having that > >> >> problem with my implementations, so I'm not sure why so many are > >> >> claiming the issue.
> >> >> This bitch is out...back to being a self-styled internet guru.
> >> >> On Jan 20, 7:02 pm, Herry <he...@redcirclemedia.nl> wrote: > >> >> > Trying to get passed the bitchfight
> >> >> > A few days ago, I described some problems I seem to have with > >> >> > ReCaptcha. > >> >> > These problems have not been solved yet. In summary:
> >> >> > On my guestbook (http://www.yawp.nl/guestbook) I get a could not > open > >> >> > socket & connection timed out error whenever I fill in some info. > >> >> > I tried a couple of possible solutions I found searching in Google. > >> >> > Funny enough everything goes smoothly on my develop server. So I > >> >> > tried > >> >> > to get different keys for the develop server and the live server, > but > >> >> > it > >> >> > made no difference. So I came to the conclusion it must be the live > >> >> > server's config.
> >> >> > But now I found that spammers somehow seemed to get passed, and > >> >> > filled > >> >> > my guestbook. This makes me wonder. Apparently it seems they can > >> >> > actually surpass the entire ReCaptcha protection. This brings about > a > >> >> > whole new aspect...
> >> >> -- > >> >> You received this message because you are subscribed to the Google > >> >> Groups > >> >> "reCAPTCHA" group. > >> >> To post to this group, send email to recaptcha@googlegroups.com. > >> >> To unsubscribe from this group, send email to > >> >> recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > >> >> For more options, visit this group at > >> >> http://groups.google.com/group/recaptcha?hl=en.
> >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups > >> > "reCAPTCHA" group. > >> > To post to this group, send email to recaptcha@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > >> > For more options, visit this group at > >> > http://groups.google.com/group/recaptcha?hl=en.
> >> -- > >> Adrian Godong > >> adrian.god...@gmail.com
> >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "reCAPTCHA" group. > >> To post to this group, send email to recaptcha@googlegroups.com. > >> To unsubscribe from this group, send email to > >> recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > >> For more options, visit this group at > >> http://groups.google.com/group/recaptcha?hl=en.
> > -- > > You received this message because you are subscribed to the Google Groups > > "reCAPTCHA" group. > > To post to this group, send email to recaptcha@googlegroups.com. > > To unsubscribe from this group, send email to > > recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > > For more options, visit this group at > > http://groups.google.com/group/recaptcha?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to > recaptcha+unsubscribe@googlegroups.com<recaptcha%2Bunsubscribe@googlegroups .com> > . > For more options, visit this group at > http://groups.google.com/group/recaptcha?hl=en.
> > -- > > Mit freundlichen Grüssen > > André Bauer
> > 2011/1/21 Adrian Godong <adrian.god...@gmail.com>
> >> That's probably true and I'm quite sure the team is on it (even though > >> there's no announcement here). I saw an update on recaptcha images > >> lately (instead of full black text, only black outline is visible).
> >> On Fri, Jan 21, 2011 at 14:18, mono...@gmx.net <mono...@gmx.net> wrote: > >> > i have the same problem with phpbb for some time so i think its > >> > definitely > >> > cracked.
> >> > changed to phpbbs own gd captcha now and spam is stopped.
> >> > maybe your site was just not visited by bots yet...
> >> > -- > >> > Mit freundlichen Grüssen > >> > André Bauer
> >> >> Can't add much more than adrian did above. It is a firewall > >> >> configuration issue that is causing your socket error. You say your > >> >> problem have not been solved yet, however, that very problem has been > >> >> solved in this group over and over again (which is why it gets so damn > >> >> old). Search the group for "socket error".
> >> >> You don't need separate keys for a localhost vs. production > >> >> implementation. I'm guessing your local machine is on a different > >> >> network than your production machine. You need to contact the hosting > >> >> company of your production machine and ask them to open some ports > >> >> (search for "socket error" to find out more).
> >> >> As for the spam getting through, quite frankly, I am not having that > >> >> problem with my implementations, so I'm not sure why so many are > >> >> claiming the issue.
> >> >> This bitch is out...back to being a self-styled internet guru.
> >> >> On Jan 20, 7:02 pm, Herry <he...@redcirclemedia.nl> wrote: > >> >> > Trying to get passed the bitchfight
> >> >> > A few days ago, I described some problems I seem to have with > >> >> > ReCaptcha. > >> >> > These problems have not been solved yet. In summary:
> >> >> > On my guestbook (http://www.yawp.nl/guestbook) I get a could not open > >> >> > socket & connection timed out error whenever I fill in some info. > >> >> > I tried a couple of possible solutions I found searching in Google. > >> >> > Funny enough everything goes smoothly on my develop server. So I > >> >> > tried > >> >> > to get different keys for the develop server and the live server, but > >> >> > it > >> >> > made no difference. So I came to the conclusion it must be the live > >> >> > server's config.
> >> >> > But now I found that spammers somehow seemed to get passed, and > >> >> > filled > >> >> > my guestbook. This makes me wonder. Apparently it seems they can > >> >> > actually surpass the entire ReCaptcha protection. This brings about a > >> >> > whole new aspect...
> >> >> -- > >> >> You received this message because you are subscribed to the Google > >> >> Groups > >> >> "reCAPTCHA" group. > >> >> To post to this group, send email to recaptcha@googlegroups.com. > >> >> To unsubscribe from this group, send email to > >> >> recaptcha+unsubscribe@googlegroups.com. > >> >> For more options, visit this group at > >> >> http://groups.google.com/group/recaptcha?hl=en.
> >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups > >> > "reCAPTCHA" group. > >> > To post to this group, send email to recaptcha@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > recaptcha+unsubscribe@googlegroups.com. > >> > For more options, visit this group at > >> > http://groups.google.com/group/recaptcha?hl=en.
> >> -- > >> Adrian Godong > >> adrian.god...@gmail.com
> >> -- > >> You received this message because you are subscribed to the Google Groups > >> "reCAPTCHA" group. > >> To post to this group, send email to recaptcha@googlegroups.com. > >> To unsubscribe from this group, send email to > >> recaptcha+unsubscribe@googlegroups.com. > >> For more options, visit this group at > >> http://groups.google.com/group/recaptcha?hl=en.
> > -- > > You received this message because you are subscribed to the Google Groups > > "reCAPTCHA" group. > > To post to this group, send email to recaptcha@googlegroups.com. > > To unsubscribe from this group, send email to > > recaptcha+unsubscribe@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/recaptcha?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to recaptcha+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "reCAPTCHA" group. > To post to this group, send email to recaptcha@googlegroups.com. > To unsubscribe from this group, send email to recaptcha+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.
warez site (and other such site) will be signing up to your forum when
they come accross a captcha, they store the image, wait for some1 to
download from their site and display the catcha for ur site.
this allows them to fill captchas without manually signing up!
try adding a second authentication box, such as a random small maths
puzzle?
hope this helps.
On Jan 6, 5:51 pm, Modern Jess <modernve...@gmail.com> wrote:
> I've been using reCAPTCHA successfully on my forum for well over a
> year. It has reduced spam down to a trickle of hand-registered
> accounts.
> As of January 4th (Pacific time) however, I have started getting
> overrun with spam. All of it from automated bots. Clearly, they're
> getting through the reCAPTCHA defenses, but I've seen very little buzz
> about it in the blogosphere or twitter.
> Has anyone else noticed a sharp uptick in spam getting past reCAPTCHA?
