Hynz

As already written you just can click https://www.geocaching.com/my/geocaches.aspx and you can even decide what type of own logs (Found, DNF,....) you want to see. But admittedly you can't restrict on certain cache types as luckycharmer want to achieve. That's scary....

Are you saying your engineers now can't reproduce the error which they acknowledged 9 month ago?

I'm sure this is a (maybe not completely intended) side effect that you and also @luckycharmer decided to hide your history of logged caches. So currently for everybody who has hidden their log history the regular search for found caches will produce this weird output. But why do you search for your own hides within the regular search? You should click on "Logs" (left side on the new dashboard) or on "Geocaches" (top of old dashboard). Both lead to this page: https://www.geocaching.com/my/geocaches.aspx And while I'm here and already stated at another thread: I strongly oppose the decision of Groundspeak to let users hide their log history. I like to see (and consider this as a fundamental basis of the collaborative nature of geocaching) what caches anybody has found in the past and what they have to say about that caches. Eg when I read a meaningful log on a cache which I also enjoyed I like to explore what other caches that user enjoyed.

For similar (but admittedly not so strong) reasons I might eventually want to see what caches anybody has found in the past and what they have to say about that caches. Eg when I read a meaningful log on a cache which I also enjoyed I like to explore what other caches that user enjoyed. And pictures in that users gallery might also be inspiring.

It *was* working in the past but GC decided around March 2022 to let users hide their find history and their gallery which IMNSHO contradicts the spirit of geocaching. EDIT: BTW why are you hiding your gallery?

No, that does not work. GC-Project only links to the GC-page (which either works or not). Try eg. with user "sucher30"

But only when the person was not lured to turned on that <censored> possibility in the settings to hide it.

Really? Sounds to me like saying "ignore the noise/smell/lighting" or are there any means of filtering out such misused (yes!) ALs?

Thankfully as owner I'm rarely plagued with such logs but this: would be my minimum requirement for all team members.

Nachdem du schreibst, dass der Multi von der Kirche weg zur Feier gehen soll: Du brauchst (notwendigerweise) nur einen erlaubten Platz in der Nähe der Feier für den Cache und nicht unbedingt die Genehmigung des Pfarrers beim Start. Die Stationen (auch der Header bei der Kirche) können - und auch Angesichts deiner eher Unerfahrenheit sollten - virtuell sein, dh. es muss dort nichts versteckt werden sondern du überlegst dir Fragen bei Stationen entlang des Weges und aus den numerischen Antworten bastelst du dir mit einer Formel die Endkoordinaten wo der Cache zu finden ist. Ich möchte nicht als Spassbremse auftreten aber angesichts deines Profils (0 Finds) möchte ich dich aber bitten Abstand zu nehmen als ersten Cache einen Multi auszulegen der nicht nur einmalig für deine Freunde sondern dann auf lange Zeit auch anderen Cachern eine Freude machen soll. Ich würde mich gerne irren aber die Erfahrung zeigt leider, dass solche Caches mangels Erfahrung der Ausleger oft nur mit Unterstützung funktionieren und nach der Hochzeit auch nicht mehr gewartet werden.

Du zerstoerst den *Thread* und der besteht nicht nur aus deinen Erguessen. Aber es ist bekanntlich sinnlos zu versuchen dir das zu vermitteln

Hmmm.... I think in my case it was obvious which conversation was the culprit. Doesn't new messages/conversations also get a colored dot?

Yes, sorry for misspelling.

Had the same problem for months. Recently I found a solution in a local forum. Hide the conversation and (if you want) rehide it. I never tried it because I thought I can not rehide the conversion without continuing the conversion by sending a new message. But that's not necessary.

When you promise that that you're not extensively using the visit feature I will tell you that it is possible. But the TB must currently be placed in a cache otherwise you have to communicate with the current holder that he/she has to support you with grabbing the TB back when you have finished your retroactively logging. 1) Grab the TB 2) Edit your found logs at (few!!) caches and mark the TB which is now virtually in your inventory to visit the cache. 3) Drop the TB in the cache from where you grabbed the TB. 4) !!!Delete the Grab and Drop log from the TB page!!! 5) Preferably edit the visit logs and leave pictures and/or text

Please be specific and accurate. This site provides a multitude of different map styles (including the opentopomap). EDIT: Sorry I read appealing.......

If the user selects "Geocaches found = private" under Settings>User Privacy you can't get any longer see the finds of that user. HHLs link was working also for such user for a long time but recently it was disabled. I consider it *very* unfortunate that Groundspeak allows this restriction which in my point of view can not be considered necessary or compulsory for complying with any local laws about privacy (GDPR in the European Union, CCPA in California, etc.)

I should have written that I checked your accounts (plural) and I expected that when you come here to the forum it was you who administered the relogging for the new account "namu_12". If it was not you then I hope you did communicate to your children (the person who wrote the new logs) what we are talking here about and that the short etiquette note was suboptimal and probably lots of wrongly deleted logs could have been avoided with a more transparent explanation.

FWIW I checked your account and found that you copied your (BTW rather short) original logs and just put in front: "Nachlog von früherem Account Lissi&Gusti" (translated: "Subsequent log from older account Lissi&Gusti") To me this is definitely not following a propper etiquette and I would confront you with questions if I would receive such log. IMNSHO the new log should explain the relation the new profile has with you and also the profile page of the new account should mention in the "About" area how it comes that this new account has (many) old logs. At least here a diligent cache owner should get an answer if he/she wonders why somebody is retroactively logging.

Either you don't like reading or don't you know how to extract a zip-file?

No

My OAR log was just deleted Can this please be considered as pressing?

Exactly! I love Multis and yes, unfortunately some owner have ambigous questions which makes me longing for some way of confirmation that I'm on the right track. But that happens more often during processing along the stages and not just at the end when calculating the final coordinates. So just a checker for the finals would often be no remedy. But I admit I once followed a Multi where the owner managed to construct a checker (certainly not the GC-Checker) which helped me along the stages.

True. Nevertheless without fighting no winning. I would contact the logger and his friend, asking them to stop by showing the guidline and ask friendly to delete the log. Without or with an unfriendly reaction I would collect hints showing the suspicious log behaviour and would then delete the log. Dependig on the reaction I probably would stop the fight but eventually I would write a note adjacent to the relogged fake log pointing out the situation as I see it.

Since Keystone merged this (IMHO not much to the OP related bug report) I would also like to report this "not disappearing yellow dot"-bug. It's unrealated to the browser or operating system. The dot appeared some months ago by receiveing two identical messages from the other party. In the mean time I had a few other conversations in the message center but the dot keeps visible in the browser on top and also (in blue but only close by the avatar of that party) in the GC-App.