Pontiac_CZ

OK, that is good enough for OP, but how would that work out for swearing logs in other languages? Are there lackeys speaking Czech, for instance?

Well, if I spotted such a log I would notify the cache owner, he has the right to delete logs on his caches. If he did not act I would notify the local reviewer. .

I know. He does not as well.

A cacher on our local forum (CZ) mentioned a few days ago that he was having the same trouble and he was NOT using a proxy. It looks like GS started checking IPs against an unreliable proxy list.

Affirmative, it does work on HTTPS on FF 45.0.2. Groundspeak, please change the link to the map on the profile page (which itself already is on https) so we don't have to manually retype the address in the address bar. Or make it work on http.

How to reproduce: 1) open the map - http://www.geocaching.com/map 2) type in "Chicago, IL" (or whatever place you wish) and press Enter (or click the search button) 3) nothing happens Firefox 45.0.2

+ 1 + 1

I guess there will be another April 19, 2016.

I do it as well. But anyway, the OP's suggestion wouldn't harm anyone and there certainly would be people who would be encouraged to write more meaningful logs (while the majority wouldn't, I know )

Basic javascript is apparently allowed, check out my profile - tabs switching and rotating of the maps is done by javascript.

OP: was your log originally different? Because such reaction does not match your (pretty kind) log. You went out to find a cache and it had not been placed yet the first time, later in your log you mention your time needed to find the cache (which was her fault) and the risk of muggling the cache in the future and she yells at you? Well, as colleagues say, being a CO is not for everyone. Definitely true. .

I do not excuse them! I just observe this kind of behavior from time to time and I think this is the reason. It usually happens on cache series. Unfortunately owners of unmaintained caches don't seem to care about fraudulent logs...

Many use scripts for logging their trip and usually don't care whether they actually found all planned caches. Is his log "universal"? I mean does it describe this particular find or does it use a few general words that might even be the same for his logs that day? If so he likely used a logging script so regarding possible NA just behave like his FI log wasn't there. Your reviewer will as well. You might try to ask him about his find. He probably won't answer which you may later mention in the NA log.

That would be sufficient and actually better than a nag on the website. But the reviewers here in the Czech republic don't do that.

So how is it with this trivial one? At least "we have it in our backlog" if not implement it directly tonight. It really does not require database structure change. You ALREADY DO SEND the e-mail to the owner of the deleted log, so just add the information from a text input to it.

We’ve already discussed situations when a cache is in a bad condition and cachers do not post Needs Maintenance log. Now an opposite case: lately I keep noticing caches that have red wrench/cross flag but after reading recent logs I realize that the owner (or whoever) cares and the cache is actually OK. The CO just ignores or forgets to post the Owner Maintenance type of log. The NM attribute can be a great tool for avoiding caches in a bad shape but it has become sort of unreliable these days. I have just gone through first 10 pages of nearby caches (the “near your home location” link) and examined every cache with a red wrench (there were 48 of them). Those with recent logs not mentioning troubles or even mentioning the cache was OK are in this list: Functional cache (has been continually in NM for:) Hrbitovni (over a year) Zamecka zed c.1 (2 months) Socha Pratelstvi (4 years) Back to the history Otrokovice #3 (4 years) Loutkove divadlo (nearly a year) U jezirek (3 years) Pomnicek Tomase Bati (0,5 years) Krizova cesta (1,5 years) Obec Kudlovice (3 years) Slovacko na dlani (1,5 years) Vydechni si (nearly 1 year) Krizova cesta na Kalvarii (1 year) Svatopluk Cech (1,5 years) Slovanske mohyly (3,5 years) Oddechni si (1,5 years) Slunecni hodiny (1 month (CO fixed, forgot OM)) Hladina (4,5 years) Jan Vilimek (1,5 years) Jan Neruda (0,5 years) Chlumska studanka (0,5 years) Spaceship crash (nearly 1 year) na shledanou (0,5 years) Mistrice BM (3 months) 23 out of 48 “red-wrenched” caches in my neighborhood (that makes 48%, which is surprisingly high!) actually have false NM attribute and distract cachers to find them while they are in a good condition. I have informed COs in the past as to what they could do to get rid off the red cross but I’m just not able to do all the work the site could easily do - to inform owners through some warning on the profile page or even on every page (not only during creation of a new listing). Every CO receives a notification e-mail when someone posts a NM on his cache (among other types of notifications), but that is only one-time action. Such an e-mail soon gets lost under the pile of new e-mails. There are people receiving so many e-mails that thay don’t read those from geocaching.com or set up a mailbox rule filtering all of them out. I’ve talked to a few people about why they still have the NM flag on their cache and they usually answer they simply do not know about it. Yep, it’s that trivial. :-) Some say they read e-mails (often on cell phones), but later when they sign in to gc.com they already have forgotten about their cache in need. And nothing reminds them there. Something should be done about this...

No fixes?

Still not fixed. I just edited my notifications (added "archive" type) and found out after I finished that all my notifications now have name "New Notification".

TriciaG: that is Czech or Slovak. I often get Italian, Spanish or languages I can't even recognize. Groundspeak ignores this issue.

+ 1

The guidelines are pretty vague in this: Physical caches can be logged online as "Found" once the physical log has been signed.

Good note and I agree, filter the "useful/liked" only within FI logs and display all other kinds as they nearly always carry interesting information.

I agree, we do not want another Facebook, but some kind of likes counter (only simple integer, no voters list like on FB) would be fine with possibility to sort logs by this counter instead of default time. I would like to have interesting stories right on top instead of having to scroll down through numerous "TFTC" and "Found quickly" which is pretty annoying. Caches already have favorite points, why not logs. But I guess that would be a great load for the database...

I do experience the same problem. I use Firefox.

The cache goes to the archive. It is just another form of virtualized existence. I do not consider it dead.