MartyBartfast

I see you're using a phone, so I just tried with my Android and again no issues. The error 500 suggests it's a problem at the Groundspeak end so unlikely to be anything to do with your phone/browser or anything you can do to fix it. There might be a passing lackey who will see this post and do something about it but I suggest you report it via the Contact Us link at the bottom of this page.

Nope

I had exactly the same, I resized the .jpg, converted it to .png and kept getting the same error, until I eventually remembered to rotate it and it uploaded. This is a very poor error message with no hint as to why it was failing.

Those clips are designed for very infrequent use, you only clip it on the cable once and might have to take it off and put it back maybe once or twice in it's lifetime. Having it opened every time it's found will probably break the clips before long.

Are you sure? I clicked the search link for item 6 on your list and it returned this, which is definitely not sorted by distance from me:

You might want to add this to the release notes thread for the change which introduced this "bug":

Maybe try this: https://support.mozilla.org/en-US/kb/Certificate-contains-the-same-serial-number-as-another-certificate

Do you really upload more than 20 images on a single log? If so I'd be interested to know how often you do so, and thereby how much if a problem it really is.

I haven't been randomly selected either, but I just tried the new logging on the Staging site and I like it, IMO it's a big improvement so thanks to all involved. This does make me think though, why don't you encourage us to test such things out on the Staging site before going live? I'm sure there are plenty of exeperienced folks who would be interested enough to go and give it a final UAT before going live on the main site.

Scenario 1: There's an area with one cacher, very few caches, and not enough critical mass to get it going, so it remains a cache desert. Scenario 2: Someone "artificially" invents some cachers, places plenty of caches, and creates a critical mass which brings people in thinking "hey this is a thing, looks popular, I'll give it a try", before you know it there's a decent little community. #2 seems the best option to me.

There are also a few groups on facebook, search for "geocaching puzzle help" groups, they tend not to give out answers but will give nudges in the right direction, also following those groups will give you some general ideas...

So then you write a bot which tries 10 times, waits 10 minutes before trying again, leave it running in the background for a week and you're done. That's not gonna happen. I hardly ever need to repeat the captcha so I'm happy with it! Last week I was entering the solution to about 30 caches in quick succession and I got the picture captcha about 3 times and once had to have 2 goes at it and that stood out for me because it's a very rare occurrence, so for me the current solution works very well - the vast majority of the time ticking the box is all that's required. If you're getting the picture captcha all the time and having to go through more than 4 pictures (which has NEVER happened to me on any site, anywhere), then it's something about your usage/setup that's making it see you as suspicious and you need to address it at your end, both Arisoft and I have suggested some things you can try. BTW the way these captchas work is a bit of a trade secret, I've seen it speculated in some places that clicking on the correct pictures containing traffic lights etc. is only a minor part of what's going on, it's also measuring your mouse activity (and maybe other stuff) while doing the clicking, therefore if the thing that prevents it tracking you when you click the "I am not a robot" box is still there when you're clicking on the pictures of traffic lights then it doesn't matter if you click on all the pictures, it will still think you're suspicious and make you have another go.

So then you successfully complete the captcha a few times, get put on the whitelist and then fire up your bot to start brute forcing the corrected co-ords unchallenged?!?!? They're not gonna do that. Considering the responses on here showing that most people only occasionally see the captcha but you get it all the time there's definitely something in your setup/usage which is triggering it so really you need to sort it out your end.

I have seen similar where a cache was Redacted (i.e. deleted) because it didn't have landowner approval, and I believe redacting the cache would also delete all the logs, but that doesn't seem to be what happened here. In my opinion the reviewer shouldn't be policing logs for validity or armchair logging, so if I had found it and had evidence I would appeal to Groundspeak to have the find reinstated. It sounds like the reviewer is overstepping their authority here.

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.

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.

Any update on the status of this? It's been a long time now and still no fix. I went out last weekend and would have liked to post pictures with my logs but couldn't because of this, and am going next weekend and would like to post pictures but won't be able to until this is fixed. I know I can post the log and then attach the pictures manually but that's a lot of effort with many logs and maybe lots of pictures, and increases the likelyhood of attaching pictures to the wrong caches.

I just got the French version too, and so have others on some FB groups. Ooh La La!

I got that, but that was specifically in relation to that answer, I don't really think that was the right place to bring up: Doing 2 challenges that were both effectively streaks was very poor. There should have only 1 souvenir awarded coloured based on the achievement, rather than getting 2 or 3. The different icon challenge should have been ANY combination of icons, not specified icons. etc.... It would have been good to have a final free form box for anything else we want to say.

I too did the survey and I thought it was poorly constructed and I'm not sure how you can derive much useful and accurate information from it. Given that there were 6 quite different challenges questions such as: How would you rate the level of difficulty of Wheel of Challenges? About how long did it usually take you to earn the easy souvenir for each challenge? would vary greatly between some of the challenges and it's not something that an be averaged across the 6 challenges. I too would have appreciated a free form box where I could have made some pertinent comments for things not covered by the multiple choice questions.

Same here with Firefox on Linux.

I think you're seeing the same problem I posted below, which is slightly different to this issue.

Some time in the last few hours the Browse map has stopped showing any caches. Ive checked with Firefox on Linux and Edge on Windows 11. I've disabled add-ons, and cleared browser caches to no avail. I've also seen it reported on FaceBook that others are experiencing the same. The Search map shows the expected caches.

They're OK, but I don't like it when the objective becomes to solve the puzzle as opposed to find the box, by which I mean very convoluted/complex puzzles which can take ages but then the cache is a trivial drive by. Being a "catch all" type means it's a bit of a mess, maybe it's time to categorize these separately: proper puzzles which needs something working out. Bonuses which just require finding a few pre-requisite cache. Challenges, which require qualification. It's intensely annoying that the caches revert to the published co-ords once solved. Caches should always be displayed on the map at the co-ords on the cache page, then if anyone cares so much about seeing a picture on the map they can remove the corrected co-ords, meanwhile those of us who want to see the real location could keep the corrected coords - everyone is happy.

But is that a symptom of their rarity, which would largely go away if they were more common? E.E. Someone going to an area for a trip is likely to specifically exclude apparently missing/disabled "real" caches and concentrate on the ones that are there; on the other hand if there's a broken/disabled webcam then it's likely to be the only one for hundreds or thousands of miles and there's a good chance the cacher doesn't have any/many webcams so they feel that they want to log it (even if it means bending the rules) while they're in the area as this might be their only chance. Similarly a disable webcam might attract people who specifically want to log it before it goes for ever. I also suspect reviewers are more lenient in allowing webcams to remain disabled for a longer time due to the fact that "when it's gone it's gone", thus extending the period when it can be incorrectly logged; whereas they are probably more strict about archiving disabled physical caches. To be clear I think Webcams have a place, but if they were to be brought back then they should be awarded in a similar way to Virtuals, in order to limit the numbers and hopefully maintain some quality.