Jump to content

OReviewer

+Reviewers
  • Posts

    289
  • Joined

  • Last visited

Posts posted by OReviewer

  1. Follow up, I had an idea.

     

    I'm wondering if the new systems are all using the API to get its data. I say this as I tried pulling this cache in GSAK via the API and I get an error that it is not a valid cache. I got the gpx from the cache page and it loaded fine. I then tried to refresh it via the API and same error. Other side of the coin is that the API is getting its data through the same route as these other new systems.

  2. It is not just you. One of the other reviewers and I were discussing this the other day. There appears to be some sort of disconnect between things at the moment.

     

    Old search sorted by newest publication, your cache shows up (19th cache on list at the time I post this).

     

    New search sorted by newest publication, your cache does NOT shows up.

     

    It did seem to take a couple of days for something to sync for the other cache I mentioned to show up on both places. My guess is this is the same thing.

     

    That said, it does appear to be an issue, especially if you can't see it on the app.

  3. How long does it normally take to get a new cache approved? I was hoping to hide one and then be able to use it in a class about 4-5 days later. Am I deliriously dreaming that it would be done that soon?

    Just a friendly comment from someone who is not your reviewer.

     

    Do you have a second account? You have no pending caches awaiting review under this account.

  4. It doesn't look like enforcement on existing caches is exactly uniform, though. There are ten earthcaches in a row at Liberty State Park, and none comply with the permit policy.

    Correct, we only do what the parks tell us to do. So far, no one in that area has said to do anything about them so I ignore the caches up there.

  5. If not, I find it a bit misleading that you posted your reply to a thread coming from someone from Germany from an area where there exist sufficiently many multi caches.

    It may or may not be misleading. I don't know that their response isn't global. I know my interpretation of what they said read to me as global. Do I know if they did any data mining or comparisons; no.

     

    The point of appeals is to be a second view and to relook at and reinterpret earlier decisions if someone feels there is an issue. I think it makes sense to look at a challenge like this more regionally but at the same time, the answer, even with different data could be the same. Maybe they decided that multi caches are a dying type and shouldn't be used. Or maybe they want less regional policy and want something that is either yes or no so they have to deal with less back and forth. I can't and won't speak for them. I can just say, their response seemed like a global response to using other icon types in a 365 non-streak fill in the grid.

  6. Perhaps I'm reading the supporting links differently, but the OP on PGC wants a checker built for individual cache types for a 365 day streak. The Help Center article explicitly excludes streaks for individual cache types. It appears that all cache types must be included in any streak challenge submission.

    I believe you are reading it wrong, or at least not the way I read it. The person wants you to fill in your 365 day grid (non-streak so the fill ins can be from any year). This kind of challenge isn't really touched upon in the guidelines other than the leap day part of it.

     

    Originally, the challenge I sent to HQ was fill in your grid with 3x mystery caches a day. When I sent it to Appeals it was for two reasons:

    1) Is a specific cache type 365-nonstreak grid an okay challenge?

    2) Advice on "are there enough qualifiers being published of said type in a given area"

     

    The answer I got was due to what is being published in the area and generally (not sure about globally), there are enough traditionals and mystery caches being published to meet this challenge going forward.

     

    I decided to do a little data mining. Just a snap shot of one state. I ran a lot of PQs to get all of the caches in PA last month.

     

    The entire state which is bigger than what I would consider the region for a cacher, there are

    -1197 Multi caches

    -3755 Mystery caches

    -21 Letterboxes

    -20 Earthcaches

     

    What more, in 2016 to date published:

    -87 Multi caches

    -466 Mystery caches

    -151 Letterboxes

    -237 Earthcaches

     

    Based on all this, I think the 'ruling' makes sense to me.

     

    I also think that if you provide appeals info for ones area to show it is doable and that there are more than enough caches to do it and caches being published to make it feasible, they may allow it. You can understand why they might not allow some of the others though. It would be near impossible to fill in say a yearly grid of virtual or webcams or letterboxes.

     

    Edit: they also said 1x a day max for these kinds of challenges.

     

    My opinion is it can become a slippery slope of how many is too many; as you can see has happened with the 2+x Fizzy, etc.

  7. There are other caches I adopted that I realize are in rough shape. If anything, they are the ones that should be disabled, not the ones that actually ARE disabled. I would not be complaining if the ones that actually do require maintenance were disabled. There's something wrong with this process. I think it stems back to the automated cache maintenance bot. The caches it identified that "might" need maintenance actually don't require maintenance.

     

    I wouldn't be surprised if more of them get notes, especially after the topic was brought to the forefront here.

  8. Many of the caches I adopted are missing, broken or in otherwise not great shape. How can I find them beforehand? Also, why would I waste my time going to find, then go ahead and adopt, then return and replace? Why not adopt then visit and replace if needed?

     

    So you know there are problems (or not even there) and you didn't disable/fix them and are mad that the reviewer saw there were problems and disabled them? You just answered your own question.

  9. I hope you emailed your reviewer and asked him to update your coordinates on your two breakfast event since you moved them since publication. You might be having people go to the wrong place...

  10. And even worst, I've come across 1/2 a dozen caches that have the state permit information already on the cache page.

    I really hope those archives were a glitch in the archiving process and not NJSP reneging on those permits.

     

    Thanks for your work O.

    The list they provided was 2 months old (of course didn't realize that until after the archive). All but one who contacted me have had their caches unarchived already. The one is a single cache where their info didn't seem to match the satellite view. Following up on it.

  11. I see that North Jersey State Parks have been cleared of caches without permits. At least Wawayanda, High Point and Allamuchy. Poor reviewer must have been up late last night!

    It happens, we serve the community and sometimes that is late in the night.

     

    I can say, it is frustrating to receive multiple emails of "I have a permit, I just never put the required info on the page". Double work is not appreciated.

  12. I filed an appeal yesterday to find out officially if first letters of geographic names is allowed. You can't game the challenge by making up odd cache titles so that problem is gone. If they say a spell the word EASY with country names where you have finds is disallowed, then you switch it to find a cache in Estonis, Albania, Switzerland, and Yemen (but enumerate all the E,A,S,Y countries) I've achieved the same challenge but in a complicated way. We will see what they say.

     

    This is strictly my opinion, not guidance we've received or anything of the sort.

     

    I see the same problem as always. At 4 letters, it is probably reasonable; that is, until we start getting $,#,!,+ and F,#,@,^ as the words to create. Then someone else thinks EASY is too easy and we get floccinaucinihilipilification and we have to judge the merits and availability of every letter in the alphabet in relation to where the challenge is located. When we have to judge, it becomes like a WOW factor and will lead to inconsistent reviews which makes for many appeals, unhappy reviewers and challenge owners, especially when random area A is okay with a 7 letter word and random area B is not okay with a 6 letter word.

     

    The other issue is that we'd inevitably run into:

    -Spell "your username", "Challenge Owner's Username", name of "my favorite sport team", etc

    -Start and end letters, third letter, or some other letter combo(s)

    -Can use county and country, or state and country, or county, state and country (fourth letter of country ONLY)

    -Is the "name of country": Germany or Deutschland?

    -Is the "name of city": Mumbai or Bombay?

     

    Again, my opinion, is that this is a can of worms I'd prefer not to see opened.

  13. Oh, great.That's what I thought. So, if I finish the Pennsylvania All Counties Challenge, I have to wait a day or a day-and-a-half to get verification? Or drive back (373 miles) another time? Rather discouraging. It still hasn't updated two of the nine counties I found caches in last weekend.

    As pointed out, it is at the posted coordinates. That said, even before that, when it wasn't, if people were anywhere near close and requested the coordinates, we provided them.

  14. It's interesting to me that a description/statement on what the container is and how it is hidden is NOT part of the submission review process.

     

    I would disagree with this. The last page of the cache submission form says:

     

    Reviewer Notes

     

    You're almost done! Use this space to describe your geocache location, container, and how it's hidden to your reviewer. The more they know, the easier it is for them to publish your geocache. This note will not be visible to the public when your geocache is published.

×
×
  • Create New...