sbied

And now I do see the fix, yay.

I'm still getting the /GC0 bug! Do I need to update something or do something to get this fix, or is your fix not a fix?

worrellsquirrel, it's been quite some time: when will we see the fix?

Just to note that I'm seeing both the "/hide/" instead of "/track/" as well as the "/GC0" thing. Chrome 120.0.6099.110 on Windows, not that it sounds like it matters.

Is there a capability to create a Pocket Query along a route that's more complex than a simple "A to B"? It seems so obvious something that folks would want to do, but if the ability exists, I haven't found it. Y'know, I want caches along "A to B to C to D to E".

Oh, yeah: not currently listed as "needs maintenance"

Filtering that I currently need to do manually after a Pocket Query that I'd like to be able to do as part of the Query: * Marked as a Favorite by at least { 1, 2, 3, 4 } cachers * Found in last { 2, 3, 4 } weeks (found in last 1 week is not useful in more rural areas) Ways to express "I don't want to waste time on caches that have a high likelihood of having been muggled": ____ * The last entry logged was a "Found It" ____ * At least N of the last M entries logged were "Found It"s

I'm a new geocacher, and have a different TB etiquette question. Is it considered to be the accepted rule that the TB travels only by the person who found it carrying it elsewhere? For example, I just found one whose goal is to get to Colorado. Cool, or uncool, for me to mail it to a friend who caches in Colorado? thanks