Corfman Clan

I saw that thread after I posted this. That seems to be a different issue though. I'm sure you're in as much turmoil over this as I am

I missed that. So that's exactly what I did. Thanks!

That's exactly what I did, choosing other, but no maintenance log showed up.

I figure my US Souvenir I was recently awarded would have been awarded on the date I first found a cache in the US. I signed up for geocaching on Jan 2, 2003. The same date I found my first cache that happened to be in the US. It's an easy date to remember 1/2/3 ?. Yet my US souvenir is dated 1/1/2003 ☹️. Is this a wide spread issue? I know, I'm shattered over this.

Okay, this used to be easy but... Tried hitting the cache needs help button when writing a note, but no maintenance request showed up. What am I missing?

I believe that apps will be able to renew the token without user intervention but am not positive on that as I have yet to implement the new user authorization in LonelyCache. From the documentation:

Alright, this time, somehow, the logs showed up on the website. Wish they did the other times.

Okay, this has happened to me on a few occasions now. I search and find (or DNF) a cache on a saved list. I enter the log, thinking I have service. The app returns almost immediately stating logging the cache was successful. Now the app shows the cache as being logged (found or DNF) but when I look on the website, it was never logged. Is there anyway to get the app to resend the log or do I have to go to the website to log it (I can't relog a find from the app, because it won't let me "find" it again).

Does it even matter? Just log it how you see fit.

Rather than put a band-aid on the problem, more people should post a Needs Reviewer Attention[1] log and ask the reviewer to fix the coordinates for everyone. [1] Unfortunately the "Needs Reviewer Attention" log is currently called a "Needs Archived" log. But that's a whole 'nuther bug report. A reviewer once said that he/she wouldn't update coords without the CO's written permission. So even if the "CO just doesn't seem to care and does nothing" the reviewer will most likely not change the coords for the CO. That's just not true, reviewers change the coordinates for caches frequently. There's even a special log type just for that.

As the owner of the Arizona Well Rounded Cacher (Fizzy Challenge), this topic interests me greatly. The AZ Fizzy not only has a date restriction, but a geographical restriction as well. Thanks for starting this discussion.

It's easy to create one yourself. Just have a note somewhere with your template. Then copy it and then paste it in to the log.

I've found many, though I don't keep track of how long it's been since the last find. I do run a website, LonelyCache that scores caches based on their loneliness.

What I've done for a few geocaches I've found that are "in the wrong state", is to log a Needs Maintenance log, requesting the cache owner update the state the cache is in to be the correct state.

[FEATURE] Include D/T rating in Found It log And what about size? Attributes? Anything else?

I enjoyed this book, as I have the previous Cliff Knowles mysteries. My only complaint, and it's a bit petty, is with the scorpion sting, its effects, and treatment.

This is an improvement on nothing, but still not very satisfying.

And how long was there no real C standard, just K&R C? It's the same sort of thing. What's the standard for GPX? It's just an open standard and there's no push for an official one either. Markdown is the same sort of deal.

The thing is, C is a standardized language for which there's lots of additional resources you can use to help you learn it. Markdown has no defined standard, so there are countless different "dialects". The only resources we can get for the Groundspeak dialect of Markdown have to come from Groundspeak, because they're the ones creating this new language. It seems like they haven't even settled on a final version of it yet, though, so they can't very well provide definitive documentation to help us. Your description of Markdown describes the state of C when I learned it. Everything evolves.

If you want your logs green and centered, just block quote them (start each line with a > character).

The bb code for quoting seems to be ignored when converting logs. Also, why is the markdown block quote in bold green and centered? Log with blockquote.

I'm sorry, that's really sad. Do you also have trouble going to the library? Eating out? Buying stuff? Pushing a cart at the grocery store? Pumping gas? Do you have a pet?

This cracks me up.

You should be able to escape the * with a backslash as so: \* Do you really think that any cacher is willing to dig through hundreds or even thousands of logs to fix such issues? One can take care of such issues in new logs but it's too tiresome to take care of them in old logs. An option to avoid interpreting logs as markdown which have not been written as markdown logs is what is needed. You're such a downer; why do you always find something to complain about.

You should be able to escape the . (numbered list) with a backslash. So, for your example, try: 3\. února