Jump to content

Bergloper

+Premium Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by Bergloper

  1. I prefer the previous user experience. Will we be able to search a cache on, after, before of between dates? This way it we can search all our finds and is it possible to search the cache which name or other attributes I forgot.
  2. Ook hier kan ik het probleem bevestigen :-)
  3. I also use steganography myself, both with images and with sound clips. I always try to host my files at Geocaching.com (= Amazon Web Services). Only in the cases that I use EXIF info or non image files I am forced to host the files elsewhere (hosting at my ISP). One of my puzzles uses images with EXIF info. Alle the images have the exact name with a suffix number (1..8). The info in the EXIF and the number in the filename are necessary to go to the next step of the puzzel. With the introduction of the proxy the filename is broken. It still is there in the URL of the proxy, but when downloading the file it is gone. The EXIF info is still available. I solved the problem with the filename by also adding this in the EXIF info. I also could visually add a number on the image. So far this puzzle can be solved again. However, when I look in the Android Geocaching.com app, these images are not displayed, they show broken. In the Apple Geocaching.com app, the images are shown correctly. To identify the problem I also viewed a friend's cache (with an image not hosted on Geocaching.com) via the Android Geocaching.com app. The image in his listing is shown correctly. I Know there are issues visualizing images in the Android Geoaching.com app. I posted a remark in the Android App specific bug reporting forum. thebruce0's assumption that images get broken because the proxy's processing can't validate the file structure is a plausible thinking track for some cases. I think it could occur when people are editing the image file structure (writing data in the file structure instead of e.g. the EXIF) or when you use a file with an invalid file structure. The images in my case were not structural edited, I just added the EXIF. As far as I know the image I use have a valid file structure. At least they show up correctly in the web interface. At this moment I don't Know what I do wrong or what goes wrong. I hope that clarity will come soon. Fortunately I only have 1 partially affected cache, but there are cache owners with more affected caches. I understand that Geocaching.com strips EXIF info by default. Still, it would be handy if we could upload images and keep certain EXIF info or add it afterwards (by stating it explicitly). That doesn't fix all the issues caused by the introduction of the proxy but it one of the many possible steps to fix them all.
  4. Since the last release note (January 14, 2020) Geocaching.com uses a proxy server to load/show images that are not hosted on geocaching.com (underlying hosted on Amazon Web Services). One of the reasons is that they want to block cookies from other domains. For certain puzzles that use the URL for solving the puzzle, this is a problem (see reactions in the release note topic). I have one puzzle that uses images hosted on my personal web space because they contain EXIF info needed to solve the puzzle. I checked my puzzle and downloaded all images. The EXIF info is still available, but the filename changed. No problem to solve this puzzle. This evening I tried to check this puzzle on the Geocaching app and noticed that the external hosted images were not shown in the app. They appear as a broken link to an image. The tother images in the listing that are hosted on Geocaching itself appear correctly. I was wondering if this is the bug mentioned in this thread or if this is a new bug introduced by using the proxyserver. I double checked the behavior with friend's cache who is also hosting images on his own web space. His images were visible in the app.
  5. Yesterday I checked the new behavior for external hosted images via the website and everything seemed to be okay. This evening I checked the puzzle via the app and I only see broken links to the images. That's not good. Should I report this separately or wil this picked up here?
  6. Thanks for the clarification. I wrote HTML with IFrames in the past, but today it is no longer common for several reasons (security, layout, ...). I also assumed that you always refer to another domain via an IFrame. I know the example of how to use the profile on Geocaching and I honestly thought that the user suplied content in the listing worked in a similar way.
  7. Which means that you have to provide the cache page on your own hosting? I suspect that this will be a problem for many people. Not everyone is able to set up their own website and edit html. There are indeed tools for that, but I fear it could be a bridge too far.
  8. I have 1 puzzle where I host images on my own website because they use EXIF info (which is removed when hosting on Geocaching itself). I now see that the URL has been changed to "https://imgproxy.geocaching.com/09a44c6d4fac8f92622d4a4177f23e18450f0693?url=http...". When I download the image, the EXIF info is still present. For another puzzle I use an mp3 file. I cannot host this on Geocaching. The link to this file on my website has not been changed.
×
×
  • Create New...