ertyu
-
Posts
278 -
Joined
-
Last visited
Posts posted by ertyu
-
-
What do you like most about challenge caches?
- A new variety of cache type, adds some 'challenge' and variety to more ordinary cache adventures.
What do you not like about challenge caches?
- The difficulty in completing most is extreme. Producing and/or gathering the information to meet the logging requirements can be tedious and time consuming and sometimes is very subjective or can not be quantitatively measured. It's often difficult to impossible to even fit all the information required into a log. Based on that effort required to log, I would bet most logs are not being vetted to see if they meet the requirements and defeating the purpose. Several challenges I've come across contain very ambiguous, erroneous or otherwise unclear requirements, making it very difficult to find. There are some I've determined are impossible to complete if the requirements are followed as stated. Many challenges do not meet the requirements in the knowledge base (https://support.Groundspeak.com/index.php?pg=kb.page&id=206). Many if not most challenges can not be completed in the local area. Many can be more difficult to complete for a seasoned cacher, even with previous finds included. Many can only be completed in very specific circumstances which leads to excluding some cachers. Most challenges I've come across require a substantial amount of travel, often to very specific and limited sites, to gather all the requisite elements. Personally I believe that challenge caches are often not balanced between finders and hiders. By that I mean, the effort required to meet the requirements and log the challenge, vastly exceeds the effort that has been put into the hide itself, container/placement/location, cache page description and the maintenance and log verification.
What would you like to see changed about challenge caches?
- No more challenges created in the future. I think there is generally a limited supply of worthwhile or noteworthy challenges. While creative new challenges do arise from time to time, for the most part they descend down the same path of other caches into the obscure and variations on the trend of those past and add nothing new.
If you could describe your favorite challenge cache type, what would it be?
- One that can be obtained in a reasonable amount of time, with a reasonable amount of effort that does not require travelling large distances or many times to complete.
What types of challenge caches do you avoid?
- I avoid pretty much avoid any challenge that I haven't already met the requirements for, am near to meeting the requirements for or plan to meet the requirements already. For the most part I've had to adopt a personal rule that I don't allow challenge caches to alter my regular caching behaviour to maintain the fun in the sport.
-
I'd certainly like to see this.
-
What browser(s) and platform(s) are you using when you encounter this problem. Do you have any plugins installed, such as NoScript or AdBlock? Is JavaScript disabled?
Firefox, Linux, sure plugins, javascript enabled. But really nothing has changed with my browser, the website just isn't working anymore.
-
I can't seem to get any additional cache logs to load on pages these days. Scroll the bottom and get nothing but "Loading Cache Logs..." nothing else ever happens.
-
Seeing it again today.
Saw this happening intermittently again a few hours ago, too, for what it's worth. Using Chrome on OS X, with GCLH addon loaded.
Been constantly missing all week.
-
Seeing it again today.
-
It's intermittent again today, sometimes there, sometimes not. Load related?
-
And now I look at another cache and I can see it.
-
Seeing the same thing on Firefox 31/Linux.
Just a blank white spot where the percentage show be. Inspecting the markup shows there should be something there, but it's not being populated.
Works on Safari/iOS8
-
Photos are uploaded not that frequently of course. However, it has become common that from time to time I find a spoiler photo where it shouldn't be. I have to check photos manually. If the website informed me about the newly uploaded photos I think it would be helpful. What do you think?
I often add a photo to the log sometime after writing the log...
It would seem that 'the system' should email the CO if the log is Edited.
How many cachers log with 'Log to Follow' and you don't get notified when the full log is submitted?
Maybe the system needs to email the CO for photos and edits, if an edit is within a certain time frame, say a month of the log?
I've made suggestions both for notification for images and edits before and whole heartedly support those notifications coming into play. They would greatly assist with cache maintenance.
-
Been seeing the same thing for a while now, intermittently I notice that I missed receiving some notifications. Mostly I've noticed archived notifications being missed. It's very hit and miss, a batch of things may happen around the same time and I'll get some notifications but not others in the batch.
-
I hate seeing recently viewed as well. Just clutters things up.
-
The main issue is that the link was convenient and quick.
Obviously, there are other methods of retrieving the same information, but they are longer and more cumbersome, especially if you don't live in the United States. I don't want another bookmark cluttering up my browser and I don't want to use five or six clicks, and two scroll-down menus, with related wait times between each. I want the convenient link to be re-instated on the page that is designed for that purpose: my account page.
Frankly, the blanket statement that the link will not be returning, when clearly it is desired by users, is concerning for me. If there was another feature coming down the pipe that will refine home coordinates and "replace" this link, then the link should have stayed until the new features were in place (and should still be re-instated until that time as well).
Seconded.
-
Miss the option to hide Recently Viewed.
-
I continue to experience this bug.
-
Besides the explanation doesn't make a lot of sense to me either. It seems like it would be a simple tweak to use all the parameters of the PQ in the database query, not just some of them, to produce the web list, dropping one of them seems silly.
You are misunderstanding how a SQL query works. It IS using all of the parameters of the PQ in the database query. The problem is when the user is asking the PQ to return more results than are allowed by the PQ (in this case 1000). When the user then sorts, they are essentially saying to the query, "instead of capping caches based on proximity to the origin, cap it based on the number of Favorites" (or whatever else is being sorted on). This logically results in a different set of returned caches.
I understand how a database query works. And also that it should be a simple tweak to query the database with the 1000 limitation based on proximity and then re-sort based on the new sort criteria to maintain the logical presentation of caches that are present in the PQ.
-
Still a BUG.
No, it's not - read Moun10Bike's explanation to my initial post. Set your PQ radius small enough that it returns just under 1000 caches and you can easily sort the PQ, keeping all the original caches that are returned.
Once I went back and tried it, it worked great! The only thing you may need to do is to keep tweaking the radius until you get just under 1000 caches - so don't schedule it to run (i.e., don't pick a day of the week) until you've got the radius figured out.
It certainly is a BUG, just because you can work around it, doesn't mean it is not.
The software doesn't produce the expected result, that is a BUG.
Besides the explanation doesn't make a lot of sense to me either. It seems like it would be a simple tweak to use all the parameters of the PQ in the database query, not just some of them, to produce the web list, dropping one of them seems silly.
-
Still a BUG.
-
Funny I go to try it today and it works, so I investigate further and find it appears to break when there are other HTML tags within the comment, for example:
<!--test<p>abc-->
If I submit that, it is entirely removed.
For online listings, I'm seeing the comments included in page source.
-
I've used HTML comments in cache descriptions before, in fact they remain in some of my listings. However if I attempt to add new ones to a cache listing, they are removed when I submit the edit.
The HTML check box is checked and comments are listed as valid HTML tags on the page.
-
I'd say Google gave about a year and half notice prior to retiring API v2 and that's only well after v3 was available. API v2 was initially schedule to drop in spring 2013 as I remember and they extended it to November. There was plenty of notice and warning. I was well aware of the changes.
-
Was burned by this again yesterday. Was walking by a cache I had previously found but by chance noticed it was disabled earlier. When I went to look it up on the phone it wasn't in the list so I assumed it was archived, so I didn't bother to check up on the cache for them.
-
I'm having trouble getting any page generated by http://www.geocaching.com/seek/nearest.aspx
Provincial or user cache lists for example.
First noticed at 10am central today.
-
Doh, nevermind.
Geocaching Blog doesn't work properly with HTTPS
in Website
Posted
The problem actually gets worse if you try to link to specific articles or archives, you end up with a 404.
Certainly SSL isn't required, but it's offered and it's not working. It's also becoming a more and more important item.