Jump to content

RCH65

+Premium Members
  • Posts

    90
  • Joined

  • Last visited

Everything posted by RCH65

  1. @Groundspeak: Why can't you just post a quick response here to show that you've understood the problem? As soon as someone writes that the issue is being "ignored," everyone freaks out again. I have no idea why you're so hesitant to involve us...
  2. RCH65

    Log Beweis

    Weshalb sollte man alles wissen/können? Du lässt Dir ja auch keinen T5-Cache von einem Taucher an die Oberfläche holen und laberst dann im Log etwas von "....war ganz schön anstrengend...". Gerade *weil* ALLE ALLES unbedingt loggen wollen, entsteht der Eindruck, dass ALLE ALLES wüssten...
  3. RCH65

    Log Beweis

    Aber geht's nicht genau darum? Diese verlogenen "schon vor langer Zeit gelöst" Logs bei denen Du sofort merkst, dass da keine einzige Minute aufgewendet wurde. Ich mag es einfach nicht, angelogen zu werden. Spiel hin oder her.
  4. RCH65

    Log Beweis

    Trotzdem empfinde ich es jeweils als "Bescheissen" wenn Leute in den Logs so tun, als hätten sie das Rätsel gelöst... sie die Koordinaten aber anderweitig "organisiert" haben. Die Tatsache, dass sie in den Logs dann ja eben *nicht* die Wahrheit schreiben, zeigt ja eigentlich auch, dass sie es ebenfalls nicht korrekt finden. Aber Du hast natürlich Recht: Während sich der physische Eintrag vor Ort durch die Regeln "erzwingen" lässt, gilt das nicht für das Lösen des Rätsels. Wir haben gestern einen Mystery-Multi Cache geloggt, bei dem man zuerst eines der unsäglichen Puzzles hätte lösen müssen. Null Bock! Wir haben dann aber (selbst!) erkannt, wo wir uns "real" in den Multi einklinken können und haben ihn regulär zu Ende gespielt. Habe das im Log ehrlich geschrieben (natürlich ohne Hinweis über das "wie") und hätte auch *NIE* jemanden angebaggert, um an die Koordinaten zu kommen.
  5. The ?dl=1 option forces the browser to download the element (and save it as a local file) instead of rendering: Use this instead: https://www.dropbox.com/s/fuh608u83qisvxz/GCA3Q55.png?raw=1 However, it's still not 100% because Dropbox doesn't deliver the correct MIME type to the browser (saying: "This is a PNG image"). But I suspect that it's always been that way with Dropbox...
  6. Check this thread: You upload your drafts from the GPSr (geocaching_visits.txt) You create the found logs based on your drafts -> the caches DO have smileys ...a few days later... You upload your drafts from the GPSr (geocaching_visits.txt) You realize that there are lots of duplicate entries you have already logged... and you DELETE those drafts All the caches of your deleted (duplicate) drafts will turn into an exclamation mark They are (finally) working on this...
  7. Oh, yes! That's what it once looked like (taken from a bug report in 2019): -> These date/time values were automatically set after uploading a geocaching_visis.txt file - based on the most recent (last) timestamp in the file.
  8. Okay... here we go! PS: Logging on STAGING was throwing an error. This is why is I reproduced the issue on LIVE with an archived cache of an inactive owner STEP 1 - There are no drafts STEP 2 - Upload drafts Let's assume that I have a brand new (Garmin) GPSr and I have found one single cache. The geocache_visits.txt file looks like this: GC3GKH8,2024-04-03T11:43Z,Found it,"Draft 1" STEP 3 - Log the cache -> Result: Cache has a smiley on all maps/lists and the draft entry is gone -> No problems so far 👍 STEP 4 - One day later - we found another cache Now, the geocache_visits.txt file looks like this: GC3GKH8,2024-04-03T11:43Z,Found it,"Draft 1" GC3GFWJ,2024-04-04T10:24Z,Found it,"Draft 2" -> Yes, the (Garmin) TXT file contains *all* found caches (up to 1000) PROBLEM 1: After uploading the TXT file, the Drafts section unfortunately contains both (all) caches. This is a real pain because the list is getting longer and longer every day. Until June 2023, the upload process ignored already uploaded drafts. STEP 5 - Deleting the duplicates All I can do now is to delete the duplicate entries one by one and then log the remaining (new) ones. This leads to PROBLEM 2: After deleting the duplicate draft, the smiley is replaced by an exclamation mark (forever): Hope this helps...
  9. Kauf Dir in einem beliebigen Geocaching Shop einen neuen "Travel Bug Dog Tag" und verwende dessen Code. Den originalen TB kannst Du dann in der Schublade "archivieren"...
  10. In other words: "Letterbox" should be an attribute and not a cache type. But that probably can't be changed anymore...
  11. But there *are* no updates (for this problem) It's just... silence... Of couse, "posts in the bug reporting forum need to be constructive and helpful to the developers". So what do you need to know? Is there anything *I* can do? Is there a workaround? Is there a timeline? Talk to us!
  12. Just enter *four blanks* at the beginning of each line to force a monospaced font:
  13. Five months later! I almost forgot that the problem still exists... and uploaded my geocache_visits.txt without prior modification... 😒 Features and functions for offline caching seem to be pushed further and further back in the prioritization.
  14. Happy birthday, little bug! Three months... they grow up so fast... 😶‍🌫️
  15. The Captchas only appear (to me) when I solve a whole series of puzzles. It obviously shows up when I check more than 10 (?) different caches in a row and *not only* when I check a single cache more than 10 (?) times. In order to avoid a brute force attack, it would actually be enough to check the latter.
  16. The official english name of "Turkey" changed to "Türkiye" about a year ago (not only in Geocaching) https://www.bbc.com/news/world-europe-61671913
  17. The CITO probably didn't count as an 'event'...? (but you received a CITO souvenir)
  18. Irgendwelche Greasemonkey oder Tampermonkey Scripts? Wäre nicht das erste Mal... ;-)
  19. Click the 'Found on' header (probably twice) to sort from oldest to newest.
  20. Hmmm... works for me in Chrome on WIN 11 Scrolled down to the beginning and printed 17 pages including 50+ logs.
  21. Have this issue every now an then. "Just create a new waypoint" is a good workaround, but not a solution. Looks like a bug in the app...
  22. The link http://img.geocaching.com/user/21ca6899-ba86-4ba8-a4a1-68bcc8cfbd95.jpg to the background image s still part of the HTML code... but the image itself is gone (Error 404). I can't remember that I've ever seen an URL having img.geocaching.com/user/something... they usually contain img.geocaching.com/cache/something... Maybe they have removed some conversion/forwarding of old style URLs...
  23. Deleting the NM log won't help. Just write an additional "owner maintenance" log.
×
×
  • Create New...