pinkunicorn

Apart from the coin on that list, in 2018 volunteers also got "Signal the Frog® Trackable Brick (Exclusive Volunteer Edition)".

1. If a TB has a clearly stated goal (which means it has to be clearly stated *on*the*trackable*), I'll make an effort to help it along. Otherwise, I'll pick it up and drop it whenever I find a new cache that's big enough. 2. No idea. 3. No. 4. No. 5. Absolutely. If I have the TB with me, all caches are too small. If I forget the TB, I find a large enough cache. Rinse and repeat...

Nice! I assume there should be something each year at least from 2005?

Being a volunteer, I get a volunteer and lackey coin as a gift from HQ each year. I wonder if there is a list somewhere that shows all the ones they've made? I've only seen the ones created since I became a volunteer in 2014(?), so I'm curious how the older ones looked.

This is from way before I become a volunteer, so nice to see some of the really old volunteer coins. I think I have all the ones from 2014 and onwards; there are a lot more lackeys on them nowadays!

Just for the record, this happens to me as well.

At least for the last few days, drafts (created with Cachly) with images don’t work properly when I try to log them on the web site later. The log gets posted but then the page just hangs, not posting the image. I’ve tried posting on the web site both via my computer and my phone.

I just saw those. If the price for getting this increased amount of souvenirs is that they are now just a flag, then I think the old way of releasing just one per month was much better.

Since benchmarks are only available to a minority of geocachers to begin with it would be nice if they could be removed from the geocaching website entirely, just like waymarks have been.

That way it can separate the reliable checkers from the others. The GC checker always tests for the proper coordinates instead of some bogus solution in the middle of the Pacific and updates the corrected coordinates for you. These are both major features. It also does not allow for random misspelled words as the solution instead of coordinates in a well-defined format, also cutting down on frustration significantly.

Will that happen to other similar errors, like the Scuba attributes on the ET Highway trail, as well?

Due to another bug ( ), I have accidentally written a couple of logs on the wrong date. After using edit log to correct the dates for the logs, the system is now in an inconsistent state. If I look at my dashboard, it claims under "latest activity" that my logs for these caches are still on the wrong dates. If I look on the respective cache pages, the same logs are shown on the proper dates.

Drafts of the Write Note type also comes up misdated to today, despite being written for another date.

It's still perfectly possible to mark caches as "needs archived" or "needs maintenance" and write a reason in your log. Before this change, quite a few people would write a "needs maintenance" log *instead* of writing a "found" log, on the quite reasonable assumption that one log should be enough to log a cache (and possibly indicate that it has problems in the process). I've seen the occasional grognard complaining over this change since Everything Is Not As It Was In 2004, but it's still an improvement.

Even though you don't see or understand the reasons for a change, there may well be lots of reasons that make it important. This can be both internal reasons having to do with performance, code maintainability, continued availability of tools and so on as well as user-visible reasons that are not obvious in your particular use case but are for others where the old version was unworkable. Frankly, expecting computer services to look exactly the same year out and year in is both a recipe for disappointment for yourself and (if some developer would listen) a hindrance to development.

Can we hope for sticky sorting as well (per list, if so - different lists require different sorting)?

The last couple of notifications I've gotten the last minutes have been back to normal again!

Well, it's not archived, but it's locked so you can't log it.

Since someone already mentioned Project-GC I'll mention cachetur.no instead. It's a great complement to Project-GC, with more detailed tools for making a tour plan, routing and things like that. There are also interconnecting tools so that you can use Project-GC to easily find caches you need for your Jasmer (for instance) and then easily insert them in the appropriate places in your cachetur tour.

The new list page generally looks good, but I've noticed an annoying problem: The page forgets settings I make (like how many items to show) when I close it and reopen.

As of a couple of days ago, all emails I get about various types of logs that I have notifications for have extra superfluous newlines between every line (Logged by, Log type, Date, etc) which means that all the interesting information (i.e. the actual log) is now outside a typical laptop screen. Please revert back to the old look. Mac OS 10.14.5 Mail.app 12.4 (3445.104.11) (I include a screenshot of a recent broken log as well as an older correct one.)

Here is what the guidelines actually say: Note the lack of any mention of log type.

Except for in-app tutorials, which they have in the official app. The "problem" is people starting out with geocaching without help from anyone with experience, and without using the official app.

Or you can post an event at the top of the mountain at 12 and say in the description that for most people that would mean that a reasonable time to start is 9, and that you yourself plan to do that. You won't have the hike technically be a part of the event, but probably more people would take part in it than if the event was allowed to be both at the start and the end (since people would then not be able to just come to the start, log, and leave).

I'm all for events lasting more than the minimum half-hour, having activities more than just meeting at a parking lot and people staying for the entire duration. None of that is hindered by using event listings as they are meant to be used; one per actual event. Reusing a listing doesn't add anything apart from confusion. As for challenges, the problem was cachers creating more and more outlandish corner-case challenges, reviewers nixing them and cachers taking them to appeals which caused a lot of work for very little benefit. Having clear guidelines (regardless of the content of the actual guidelines) eliminates this problem caused by people bending the too-vaguely-defined rules too far, and I feel that is a good thing (which is not really the subject here, though).