AZcachemeister

More 'hobby code' on the site. These are not things that happen on professionally produced sites.

So true! The OP should go out and find some caches rather than complain about how many (that they haven't found) can be included in a PQ. A PQ can include 1000, will that be a good day for you?

Then the system is faulty. So? Delete the entire log and invite the poster of the spoiler photo to log again without the photo. @ Moun10Bike Plenty of resouces to produce 31 souvies for August, but no resources to fix an actual site failing? Tsk, tsk.

I think that's pretty clear already. Yup, bucketloads of evidence in the positive for that call.

This is what immediately came to mind for me. There is a whole series here in AZ with this on the cache page (or at least there were...I haven't checked them recently). Similarly, there is at least one other powertrail with a regular size cache at either end containing materials for maintenance of the caches on the powertrail. Grab a few replacement containers and logs as you begin the trail...no need to post a DNF, and no need for the owner to do maintenance...other than restocking the supply caches.

This is a very important project that every Lackey will be participating in. They all will be donning bright orange headbands and going out and locating geocaches. This is NOT something to be taken lightly. Nothing says we mean business more than an orange sweatband. The entire month of August is holy and sacrosanct for geocaching. Everyone will be expected to make sacrifices in order to find a geocache on every day of the month. Personally, I will be fasting during the day and only eating a light meal after sunset every day of the month to keep myself in top shape for this event, as well as methodically circling around every geocache 7 times before finding it. I also will be teaming up with a group of other cachers and going around to people's houses singing geocaching tunes, as well as mailing geocaching greeting cards to all my friends and relatives. On the sacred day of August 17th, I will be dressing up as Dave Ulmer and dropping full ammo cans under large evergreens everywhere. It will be a happy day! I'll be wearing a bright orange jockstrap (and little else). Look for it!

Meh. Wouldn't have slowed me down unless I came within visual range of a residence before getting to the cache location. Even then I would probably need to see someone who appeared concerned with why I was there before I became concerned myself. In which case I would approach them and ask if they knew anything about Geocaching so I would know if a NA needed to be posted or not.

...and your TB will have a series of logs outlining your activities with it.

No longer possible. Back in the day these were done, but not commonly. There seem to still be a few around that have been 'grandfathered in', but today a cache must be at a fixed location.

No way of knowing, the 300 favourites from 2% of premium members could still mean 100% of premium members awarding a favourite point since it was possible to award a favourite point, while the 10 favourites could just mean the CO'd buddies dived out and grabbed the cache and all gave it a favourite point despite it being a film pot behind a sign that was soggy within two days of being placed. Interesting hypotheticals. Have you ever seen this in person? I've got lots of friends who cache. I can't imagine any of them giving a favorite point to a crappy cache, though I know it happens occasionally. The ET Highway is a good example of this. If you randomly pick one of those copy/paste film cans, you'll probably find a favorite point on it. I certainly can't picture any ten cachers giving favorite points to stinkers. I would say it's improbable to the Nth degree. But getting back to my question: Would such a challenge work, as a compromise for the OP? I would suspect that both caches were pretty good. Knowing the date of publication would also be a relevant factor. In any case, it is apparently no longer possible (by any stretch of the imagination) to reward cachers for owning caches that have been selected by their owners peers as the best-of-the-best. I have not been a huge fan of the Favorites Points system from the beginning...who knew my disdain could sink even lower.

I wouldn't want to broadcast the fact that I deleted a photo or log to the general population. It is none of their business. In fact, it is only between me and the cacher posting the log/photo. Someone may have such a spoiler log or photo already downloaded to their system that they may be unaware was a spoiler until the deletion notice went through. 'Oh, look...a spoiler photo was deleted! Yes, I have that one here in my system.'

This could be handy, but considering we have had an idea to remove missing TBs from cache inventories for two or three years now (that has yet to be implemented despite official approval of the concept) I have ZERO faith that this idea would be developed.

Predicted way back in the first few pages... Groundspeak knew there probably wouldn't be a huge uprising of discontented Europeans...and they were (apparently) correct. If indeed there had been such an uprising, I have no doubt that a contingency plan was developed...just in case. Nothing to see here, you should all go back to your normal Geocaching activities. For those of you who felt the need to carry the protest to the maximum extent (and cancel/not renew you memberships), we salute you.

There are enough idiots in here, 'As he looked in the mirror'.

I logged in under my reviewer account to comment on these. Don't try to copy them, they're grandfathered, but they are not usable as a template for a new challenge. When a challenge offers multiple routes to completion, all of the routes must meet the challenge caches article. OY! JESUS, JOSEPH, AND MARY SAVE US! We are being regulated into oblivion. No wonder the pointless lampskirts and mindless powertrails are taking over. But, let's focus on quality...yeah, right.

You too? I thought it was just me...

I'll take a nice-size container large enough to accept the TB I need to drop off, dry inside (and of course with a dry log), at the end of a moderate hike (2-3 miles isn't too far to go for something like this), at an interesting location I might not have visited otherwise. Up in the mountains, down by a lake, out in the desert...none of that really matters.

Duly noted, thanks for the heads-up!

Back in 2011, I also wanted to hide a 'Favorite Points' challenge based on ownership of quality caches. In those days, the guidelines linked to on the cache submission page were very short and simple, and as far as I knew they were the 'rules' of Geocaching. The guidelines in the Knowledge Books existed, but were not prominently displayed or linked to. I knew nothing about them, since I prefer to go out caching and not spend time poking in obscure corners of the website. But, as they say, 'Ignorance of the law is no excuse.'. So, the Reviewer published my challenges right away. Then someone posted a note about this (then obscure) guideline that even the reviewer didn't remember, and the caches were retracted/disabled. So, (in order to have the caches published) I was compelled to create a less elegant point system that makes it possible for non-owners to qualify, but much easier to qualify if you own good caches. FWIW, these are my only PM caches: Favorites Challenge-Level 250 Favorites Challenge-Level 500 Anyone who wants to copy the concept I used is hereby granted formal permission to do so.

If I wanted to do this, I would use Google Earth, the Groundspeak .kml, and the Google Earth measuring tool. Granted the locations of the various caches tend to jump around a bit, but I think the derived distances would be close enough to get a good idea of the overall distance involved with a particular route. You could do point-to-point, or zoom in really close and follow the trail fairly precisely if you like.

That's why they developed the API...so they wouldn't need to provide this kind of functionality directly on the site. I can't say for sure, but perhaps someone could develop a little program using the API to only download PQ results? Maybe the program could also D/L the .gpx files for all the caches I logged today, too, so I wouldn't need to visit each cache page and D/L them separately?

It's pretty rare for me to delete a log. When I feel something minor needs to be changed or the logger didn't post a photo or send verification (for my virtual), I usually send a message asking them to correct the situation and then delete the log if they fail to comply...so I wouldn't want or need to send a reason when deleting the log. If someone posts a blatant spoiler or uses profanity, I'm going to make them ask me why I deleted the log.

This is one of the handy features of the API, or in other words...GSAK does this.

I really don't see the connection unless the OP was one of the 'finders' whose log may be in question. In the quoted log by the alleged CO, my only concern would be that they didn't visit the cache location soon enough after a 'rash' of DNFs to preclude the bogus 'I was there so I deserve a smilie' logs. Seriously, this is Geocaching: go to the posted co-ordinates, find the container, and sign the log. Then claim your find for the cache. NOT: go to the posted co-ordinates and claim a smilie because you were there.

So why bother even posting to this thread? The whole premise behind the thread is for those that *do* care about souvenirs, enough that they might consider taking the month of August off from geocaching to avoid having what the feel are pointless souvenirs cluttering up a page that they *do* occasionally look at. Unfortunately it seems to have devolved into a bunch of people that don't care about souvenirs belittling those that do. For the same reason that you are posting to this thread...to express an opinion on the subject matter. Climb down off that horse buddy, it's about to topple over.