Jump to content

Corfman Clan

+Premium Members
  • Posts

    478
  • Joined

  • Last visited

Everything posted by Corfman Clan

  1. Actually we don't know if these data are collected with the new API. Obviously it was known with the previous API since the quota was per app, but now the quota isn't per app so the data very well may not be known.
  2. But then you're not using the bookmark list, you're using the pocket query. At any rate, this statement seems rather specious.
  3. Apps aren't doing it, "on their own", unless they are not following the API partner agreement. Apps should only be using the API for a user if the user allows them too and in the manner authorized. The user is able to revoke an app's authorization any time. I'll also suggest that it is a user's responsibility to understand what authorizing an app entails.
  4. So don't putz around for 30 minutes with the map on your mobile. I will say, that for mapping, the lite cache option should be used. That's essentially why it was added. Lite-cache gets no description, full cache does. I don't know what your mobile app is doing, but perhaps you ought to complain to it's producer on its inefficient use of your cache quota.
  5. This seems oh so silly to me. How many caches does one really need to get in a 24 hour period? More than 26,000? Previously, for premium members, the limits were 6000 full cache details and 10,000 lite cache details. Evidently that was per app, though I suspect that wasn't the original intent by Geocaching HQ. Now, the full details quota has been updated from 6000 to 16,000, though for all apps. That's a big increase, 167%.
  6. In general, the type of browser and device it is running on is known to the server responding to the web page/map request. Yes, there are differences in how the device figures out where it is, but the "map" most likely does know what type of device it is serving.
  7. So I had reason to create a new user account and I wasn't able to add a space into the user name. Anybody have any idea when this restriction started? Spaces seem fine for all the user names that have them, such as my current one.
  8. Aren't the caches locked? If so, they can't be logged.
  9. I don't believe this is the case. Geocaching HQ now requires TLS1.1 support, so TLS1.0 is no longer adequate. There has been no mention of requiring TLS1.2 support to me, as a geocaching API partner. My app, LonelyCache, uses TLS1.1 and is working fine. You may be thinking of the authentication mechanism. Geocaching is moving to requiring oAuth2 authentication along with moving the API from SOAP to REST. oAuth2 isn't required yet, but will be in a couple months.
  10. Someone couldn't find one of my caches and threw a replacement down. I told them I wasn't happy they did that and to change the log to a DNF or I'd delete it. One cache, I found three different throw downs. I've found a cache one day and the next, someone couldn't find it and placed a throw down. I think Geocaching is turning into Pokémon, got to "catch" em all.
  11. I know last summer, Geocaching HQ made some changes to conform to the GDPS. That may very well have impacted the functionality of some apps. Also, they converted from TLS1.0 to TLS1.1 (Transaction Level Security) which also may have affected some apps. Both of those changes impacted LonelyCache, the latter causing its users to no longer be able to authenticate (authorize) with Geocaching.
  12. LonelyCache has been running on the REST API (I personally would not call it JSON based) since early last December. It was a fair bit of work to convert from the SOAP API, however I think it is currently running better than it ever has, as it forced me to look at and resolve some issues I had been ignoring. That being said, LonelyCache has yet to convert to the new authorization mechanism that is part of the transition Geocaching HQ is having their API partners go through.
  13. Seems like somebody used an inner join instead of an outer join, but what do I know?
  14. Any help on this? I still can't log in via Facebook and I cannot connect my accounts either.
  15. @SnowstormMK And that doesn't seem to work either. I get the same empty white spot as I mentioned above. So I guess my account is now in some sort of limbo for allowing logging in via Facebook.
  16. Well that's obtuse. Perhaps the website should let one know that is needed when a connection isn't found?
  17. I thought I'd try logging in via Facebook to see how it works. I'd never done this before. I get redirected to Facebook fine, authorize, then when I get redirected back to Geocaching, I end up seeing a blank page (well, the header, footer exist, but the main part is plane white. Anybody else see this? The redirect Url: https://www.geocaching.com/account/join/link?facebookAccessToken={edited-for-this post}&facebookAccessTokenExpirationDate=03%2F25%2F2019%2000%3A18%3A08&returnUrl=%2Fplay#_=_
  18. Don't know why I didn't think of this before posting my question, but I thought of it shortly after. Sort of like finding a cache immediately after PAF with no answer I guess. I checked the size of the default avatar and it's 250x250.
  19. What size should a profile picture be? The allowed size was increased awhile ago, and now my image (and others' images) show up funny here in the forum. The settings page shows what size a banner image should be, but not the profile picture's size.
  20. Thanks for mentioning LonelyCache! I used to be an officer in my employer's camping club and a fellow colleague told me about Geocaching on one of our outings. Shortly after, I found a few with my family and we found some on a vacation. A few years later, a friend told me about the Deep Southwest Geocaching Project, or DGP, that scored caches and ranked cachers by the lonely caches they found. I really enjoyed that side of the game, finding hard to get to caches. That site went defunct in 2011, so I started LonelyCache. I don't geocache nearly as much as I used to, but I think that's what keeps me geocaching now.
  21. I saw that thread after I posted this. That seems to be a different issue though. I'm sure you're in as much turmoil over this as I am
  22. I missed that. So that's exactly what I did. Thanks!
  23. That's exactly what I did, choosing other, but no maintenance log showed up.
  24. I figure my US Souvenir I was recently awarded would have been awarded on the date I first found a cache in the US. I signed up for geocaching on Jan 2, 2003. The same date I found my first cache that happened to be in the US. It's an easy date to remember 1/2/3 ?. Yet my US souvenir is dated 1/1/2003 ☹️. Is this a wide spread issue? I know, I'm shattered over this.
×
×
  • Create New...