Jump to content

Hynz

+Premium Members
  • Posts

    532
  • Joined

  • Last visited

Everything posted by Hynz

  1. Really? Sounds to me like saying "ignore the noise/smell/lighting" or are there any means of filtering out such misused (yes!) ALs?
  2. Thankfully as owner I'm rarely plagued with such logs but this: would be my minimum requirement for all team members.
  3. 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.
  4. Du zerstoerst den *Thread* und der besteht nicht nur aus deinen Erguessen. Aber es ist bekanntlich sinnlos zu versuchen dir das zu vermitteln
  5. Since there is no rule every cache can be labeled by an owner as TB-Hotel and I don't think any reviewer will refuse publishing even when the cache size is given as micro. Recently in my area a TB-Hotel was published as a Multi-Hour 5T Nightcache But IMNSHO a TB-Hotel should be easy to get to and should invite cachers travelling through the area to quickly stop and exchange TBs. So when your gadget cache is just a fancy out of the ordinary box everybody can open then OK but when you need special equipment or need time and patience to open it then I would say please don't advertise it as a TB-Hotel.
  6. Hynz

    Message Center

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

    Message Center

    Yes, sorry for misspelling.
  8. Hynz

    Message Center

    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.
  9. 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
  10. Please be specific and accurate. This site provides a multitude of different map styles (including the opentopomap). EDIT: Sorry I read appealing.......
  11. 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.)
  12. 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.
  13. 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.
  14. Either you don't like reading or don't you know how to extract a zip-file?
  15. My OAR log was just deleted Can this please be considered as pressing?
  16. 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.
  17. 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.
  18. 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.
  19. Please! Nobody - neither cache owner nor listing reader - are interested in long copy&paste texts which have no relation to the very cache they are posted to. Either take your time to leave a meaningfull text (which does not necessary have to be long and can also be writen later at home) or if you can't be bothered to respect the intention logs have been introduced keep them at least short so we can easily ignore them.
  20. Hynz

    Can't log anything

    I know it's not fully Groundspeaks fault but I can't help regretting this development of webdesign. Even on new technology it needs absurd CPU power and often is accompanied with breaking old and good conventions.
  21. Seems to be that the new logging experience is to blame. And there is no workaround. Hope it will soon be rectified.
  22. So, you expect the volunteer reviewers to go through every cache with a fine tooth comb before they Archive the caches with non-responsive owners. In my opinion that's *exactly* what reviewers should do. At least they should read and digest the last logs. And I want to believe that many reviewers are doing this. But whenever a reviewer of the other kind is archiving a perfectly findable remote cache of an inactive owner we have again such a heated discussion. I also think that many of those who vehemently demand to archive every cache with two vague DNFs and an inactive owner have in mind a micro already replaced by three throwdowns in the middle of a cache dense area.
  23. So your online logs do not contain these stories? Why do you exclude owners and other finders from that fun? Even when some of your stories are only loosely connected to the cache find, as an owner I would be much more interested in those than in an other short and generic logtext.
  24. The easiest (but still cumbersome) way is to click on "View All Logs" down on the listing page right before the logs start. There you can at least quickly "jump" 50 logs ahead.
×
×
  • Create New...