Pontiac_CZ

+ 1

The other one ("auto-disable after a time with no action") would be fine, I guess, as there are owners who have only a single cache and don't plan to hide another one. An unmaintained cache shouldn't be offered to the audience and one would know directly from the map that the cache should be avoided. Maybe some sort of nag on the main page could be enough, as suggested in this thread.

It is a question whether to bother with the red wrench/cross anymore. There are caches around me (like this one) that are maintained but the inexperienced owner just doesn't care about getting rid off the NM sign. There is nothing that pushes owners to do that.

I agree with temporarily switching to PMO and then (when already in PMO) change the cache location so that they don't know it. I suppose those nicks are basic members. And completely ignore them as angry reactions are what they're after. No reactions = no fun for them. It won't last more that a few months.

CZECH / ČESKY Hraju hru Geocaching Geocaching je světově rozšířená hra vhodná i pro rodiny. Spočívá v ukrývání a následném hledání schránek (keší) pomocí GPS přijímače. Na světě je více než 7 500 000 hráčů a 2 500 000 keší ve více než 170 státech. Momentálně hledám kešku v této oblasti. Podrobnosti můžete vidět na mém GPS přístroji. --------------------------------------------------------------------------------------------------------- Kešky se vyskytují od velikostí velmi malých jako je guma na tužce až po veliké jako třeba sud, ale vždy musejí obsahovat papírový zápisník nebo list papíru, na který se hráč podepíše jako důkaz nálezu. Schránky jsou často maskovány, aby je nebylo lehké najít. V keši mohou být předměty na výměnu kromě věcí nebezpečných, jídla nebo věcí nevhodných pro rodiny s dětmi. Více informací najdete na www.geocaching.com.

I personally would be motivated by the past nice logs and possible future nice logs if the cache goes on. Do I get you right, Cezanne, that in this theoretical situation when your cache is in a bad condition or lost for a longer time and someone finally posts NA, you expect other cachers begging you to fix it?

You'll have to put your DNF count within the BIO box like we do. The overflow is no longer allowed...

I have to defend the NA poster in this case - it looked like the CO lost interest in that cache (9 months disabled with no reaction!) so he correctly posted NA. Here in the Czech republic such disabled caches get usually noticed by our reviewers after a few months and get a note with 30 day ultimate before archival. I would not hesitate to post NA myself as well, but I would be aiming not for the archival but to get the CO comunicate, fix and enable the cache. EDIT: the CO apparently needed such an impulse as the cache got up and running in twenty more days!

That one is really weird, my FF is stuck with "Connecting...". Can't even load the profile page now. Interesting bug.

I agree, this has to be fixed, changing the content instead of the format only is a serious bug!

KaRue: the DNFs start in May 2015, your NM was in November. The cache is apparently not there and it exists now in the form of abandoned listing. If it was in my area I would definitely post NA. (actually, if I were you I would post NA in November instead of NM so you were really nice to the CO which doesn't seem to care anyway)

True. But the more time passes by the more I think this is one of the few good changes Groundspeak ever introduced. In the past many times I saw logs using colors and/or obscure fonts, they were sort of visually breaking the logs flow on the cache page and were not so pleasant to read. I believe fancy formatting should go to listings only. The experiences geocachers share in their logs should focus on the content, not the form. And remember e-mail notifications with tons of UBB code in them, that was really annoying to read. But I'd rather see Groundspeak invest their time and money into fixing things, like the map with occasionally-unclickable icons etc.

I confirm this issue (Firefox 43.0.4). Looks like after pressing Escape key the Markdown guide is still in place but invisible hence mouse wheel events are captured by this invisible window. If I open the Markdown guide again and close it correctly using X in the top right corner, scrolling works like before.

Logs (and preferably the nice ones ) are the only reward for an owner's work. So I feel that if I visited a cache and did not let the owner know about it through my log... that would be selfish. I would only take and would not give.

1) Too much white. This change was about Markdown - why did we lose the alternating background color in the logs? 2) I understand you removed the old parser which took care of UBB/HTML code in the logs. Then why not display the old logs without any formatting at all? You would have no complaints about converting dates (3. února -> 1. února) to lists and so on. Just display the old logs as a plain text, that is easy to do.

Well, this feature request is still relevant, I guess. There are many users which are responsive and willing to take care of their caches, they just somehow forget to remove the NM flag. Like this one - 5 ouf of 8 caches in NM condition. It was 6 originally, but I recently found his "P&P#3" and dropped a note that the cache was alright and only needed Owner Maintenance log to delete the red cross. Shortly after my note the owner did that.

Nannibella: why go TFTC, just continue writing about what you experienced when out caching. Owners appreciate the log content, they're not as much interested in the log form (at least I am not ). And they're even less interested in reading e-mails with the text mixed up with BBCode... But anyway, I agree with you that Groundspeak shows sort of disrespect towards their customers. I guess it is technically possible for the old logs to stay rendered the old way.

I love it too, the OP's idea is perfect. It is abuse-proof - what could be abused? Yes, someone might intentionally mark the item as missing (although it still is in the cache) so it would go into the "ghosted" state. But the next cacher after him who discovers or retrieves that trackable will bring it back to the normal state. The idea is very well described and I think it would work perfectly. Many caches would finally get rid off missing trackables.

You're right about this, cachers rarely use ordered and unordered lists in their logs (and if they do, they write it manually, in plain text) but I guess it's a third party editor (?) so they just left it there.

Or if one is shy and doesn't want the CO to get mad at him, he can directly contact the reviewer who published the cache and let him know about it.

I had already put my Nexus 6 screenshots of new cache notifications in the new cache notifications reformatted thread in Website forum. And here you have new log notifications from my cache in Gmail app - I have to scroll down to see a two line log.

I too was about to get a Maxpedition Sitka, but after viewing tons of review videos I bought an enhanced version of Sitka - Vanquest Javelin Vslinger . It has well thought-out organizing options with many small pockets for all the stuff I need in geocaching.

Colleda: you're probably looking at the old style notification as the new one does not show up nicely on phone displays. But in case it really does for you please provide a screenshot, I am most curious.

Today I received a newly formatted e-mail notification of a new cache. I had to scroll down to see all the info. And Nexus 6 has a LARGE display. Comparison - old and new: Why is the green field around the logo so wide? Why the line spacing?

I agree as well. Marking logs as "useful" (or whatever word) would be something like FP for logs. And the great thing would come afterwards - the possibility to sort the logs on the cache page according to "useful" points gathered. I like to read nice logs on the cache pages, but it is annoying (and devastating my mouse roller ) to go down through logs like: "." ":-)" "TFTC" "Found on our trip with ***" "Found quickly, thank you." "Today we decided to go for a caching trip. The weather was fine... (10 more lines about the trip copy'n'pasted to every log that day). This was a quick and easy find. TFTC." It's nothing against people who don't support the idea, they just could ignore it (just like I ignore FPs on caches due to using GCVote). For the rest it would be really "useful" feature.