Jump to content

Can We Please Get a New Captcha?


C3GPS

Recommended Posts

From the service provided it states that reCapcha is used against fraudulent use. Quote: 'A seamless fraud detection service that stops bots and other automated attacks while approving valid users.' On Geocaching you can only access a page if you are a registered member. So i can't imagine any bots or anybody else messing with attempts to check if the coordinates i think as correct are put in the solution checker. At the moment it is nearly impossible to get a quick check. Especially if you have a trail of mysteries. If i get a quick one, or maybe two, the next will annoy so much I just quit the trail.

I there has to be an extra step, I have noticed a much friendlier one. See picture attached. You have to click on pictures in the right order. A much faster way to get through it.

SmartCaptch on Yandex.jpg

  • Upvote 1
Link to comment
17 hours ago, HaSiYoTi said:

On Geocaching you can only access a page if you are a registered member. So i can't imagine any bots or anybody else messing with attempts to check if the coordinates i think as correct are put in the solution checker.

 

I know many registered users who would use a bot if it is possible.

  • Upvote 2
  • Funny 1
Link to comment

I am also starting to get more and more annoyed with the recaptcha. Once is fine, but more and more you have to solve more and more pictures. When using a checker once or twice, that's no problem. But with, say, a trail, meanwhile, it takes more time to get the checker to check than solving a 250-piece jigsaw puzzle. In a manner of speaking.

 

I don't understand it either; when logging in, I already have to solve 1. Proving that I am not a robot. Then why for each separate checker again?
That there are people who would like to use a bot may be. But they will find a way around it anyway.

 

Translated with www.DeepL.com/Translator (free version)

  • Upvote 3
Link to comment

Same thing for me, when I have to solve a series of mysteries, on the 8th or 9th resolution, the captcha is displayed and sometimes it takes 4-5 tries even though the selection is good.
There should be a condition for this captcha not to be displayed, for example, if you're a premium user or if your account displays 500+ caches or, depending on how long you've had the account, an option to tick in your profile (after a certain number of found it). Really tiresome on series like geoart.

 

Edited by OliLesp
Link to comment

I very rarely get the photo Captcha when checking co-ords so not a big problem for me.

 

I'm wondering why I don't get challenged when other do, is it likely to be due to which cookies we're accepting from GC?

 

The photo challenge is invoked when clicking the "I am not a robot" box either fails or is inconclusive, I know that this box isn't just asking a question -  it performs checks against various things in your session activity so could it be the way that different people check this box or run their sessions that is triggering the pictures more for some than others.

If we knew what scenario(s) cause the photo challenge to be invoked then it might be simple to change something on your setups to make it less frequent and therefore less painful.

 

Link to comment
1 hour ago, MartyBartfast said:

If we knew what scenario(s) cause the photo challenge to be invoked then it might be simple to change something on your setups to make it less frequent and therefore less painful.

 

If you knew that, you could make a loooooot of money selling the method to scammers/hackers on the dark web. Captcha-bypassing is valuable stuff.

 

What I find interesting is that, if coordinates are checked via the API, there is still a 10 tries per 10 minutes limit, but there is no Captcha. That is, the method that is objectively easier to automate does not perform any bot checks. Why?

Link to comment
24 minutes ago, Hügh said:

If you knew that, you could make a loooooot of money selling the method to scammers/hackers on the dark web. Captcha-bypassing is valuable stuff.

Not really, I'm not talking about any deep analysis of the tool, but there's clearly some usage difference between me, and those who keep getting the pictures and it shouldn't be that difficult for someone to work out what features trigger it by flipping normal controls or tweaking the way they interact with the site. E.G. if these folks don't allow any cookies from GC then they could enable cookies as a trial and see what changes.

An example in reverse is I just opened the site in a "Private" browser tab,  and I then get challenged, sign in in a "normal" tab and I don't get challenged - I doubt that will be a revalation to anyone trying to crack the captchas and if it is I'll happily take the ££££.

Taking this into consideration a bit of research into what the Private tab restricts, and consider whether the OP has any additional security features turned on to restrict some similar functions would be worthwhile.

If I was having this problem I would try things like this in sequence to see if I can find one which produces fewer challenges:
Dont use a private tab

Accept all cookies

Disable any ad blockers

disable any script blockers

disable any additional security features in the browser.

bypass your VPN if you use one

...

 

All temporarily while investigating and then put them back, if I found one feature which was causing the additional challenges then I'd look into whether GC can be whitelisted somehow in that feature.

 

 

  • Helpful 1
Link to comment
7 hours ago, MartyBartfast said:

I very rarely get the photo Captcha when checking co-ords so not a big problem for me.

 

I'm wondering why I don't get challenged when other do, is it likely to be due to which cookies we're accepting from GC?

 

The Captchas only appear (to me) when I solve a whole series of puzzles.

It obviously shows up when I check more than 10 (?) different caches in a row and *not only* when I check a single cache more than 10 (?) times.
In order to avoid a brute force attack, it would actually be enough to check the latter.

Link to comment
2 hours ago, RCH65 said:

It obviously shows up when I check more than 10 (?) different caches in a row and *not only* when I check a single cache more than 10 (?) times.
In order to avoid a brute force attack, it would actually be enough to check the latter.

Yes, and that is indeed the big problem with the built-in checker. All the popular external checkers impose penalties (e.g. no more tries for x minutes) only when you guess wrong. As long as you only get "green", you check away all day long.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...