sloth96

So is this intended to end time varying content going forward? Some puzzles change the image as a function of time. Some did time of day. Also some other features as well took advantage of this. Or is there another approach for dynamic content? This seems the end of an era that proxies did not help with.

Thanks for the update.

Has anyone noticed if this is fixed or not? On the GSAK board I was posting about some inconsistencies between PQ's and API calls as well as between different API calls. Oddly they occurred on the same date. However they occured with archived logs. It also would be good to know if this is a small patch just for this date or larger scale fix.

Has there been any change on this or is it still not possible to add caches from the android app to the watchlist? I took a look but could not find anything.

Chasing those sorts of caches is a game of chicken. So long as folks are having fun i dont see the harm and it keeps the gameboard fresh. We dont all cache the same.

A bunch of friends in the area chase resurrections. (Some places call them lonely caches.) They are caches that have not been found in a year. It always get their attentuon when i call them as they are walking away from a cache. It is a way to celebrate with them. As these caches usually are rarely found it is not many emails on a daily basis. They generate more archived, reviewer notes and disabled than finds.

Interestingly enough, my watchlist says 14602 caches are in it when going in through the API with GSAK. The 5000 above is through the web interface. I wonder why the difference.

I just tried adding a cache to my watchlist and received this error. Your Watchlist [You have reached your maximum number (5000) of caches to watch. You will need to remove another item before adding this to your watch list.] Is this to be expected? I cannot find this limit documented anywhere. The bookmark list limit is 1000. Does this limit extend to the ignore list as well? Thanks.

In the 06.22.2020 update to the API, there was a log type filter added to the get friends logs call. It would be nice if this was also added to the GET GEOCACHE'S LOGS and GET GEOCACHE LOG queries as well. This would allow users to only download relevant log types. This seems of particular use when one is in an area where connectivity is slow or unreliable to only fetch desired information. For events (CITOS, Megas, Events, GIGA's,...) , this would be a great way to find announcements among all the Will Attends. For high difficulty caches this would be a way to focus on the Find and maintenance logs lost in a sea of DNF. I am sure developers will be able to come up with other uses of this capability. Adding this to the get geocaches calls as well would also be nice. Log Type filtering would be great for all operations that can fetch logs.

Howdy, While we would all rather not be dealing with the spam, the server seems to be keeping up with the load and messages seem to keep coming through and are responsive both in my e-mail, android app, and web interface. This may likely be the worst stress test this system has ever seen. It is handing the load well from my perspective. Cheers all!

Howdy, with all the spam floating around, something interesting has happened on the group message in message Center. On the android app they all show as having different sender icons. They show up in my e-mail as having different senders. On the website in the messenger feature they all appear to come from one user. While the spam will likely be stopped, this appears to be a bug in the web messenger feature. It is appearing in both chrome and firefox for me. Hope the storm stops soon.

Oh I understand that. When this first started I cancelled my event. However if it means no events for the next 5 years then I might change my thoughts. The flip side is a 25 person event with 20 disappointed people is better than a 0 person event with 45 disappointed people.

Understood but I am trying to understand what techniques are being used elsewhere to manage events. Government rules can change or if the current restrictions stay in place indefinitely, what do alternatives look like. It is nice to be ready.

With COVID-19 restrictions going around, some places have restrictions on gathering sizes. How does one restrict the size of the group at events to allow the event to occur and remain legal within the other rules? HQ uses a website and has used event brite in the past to basically issue tickets to limit the flow to that cache. (iirc tickets were issued per person not per caching name.) They also were going to have special rules in place for the 20 year celebration. One possibility that came to mind was to break an event into a series of 15 minute gatherings and issue tickets for the gatherings so that at no time there is more than the legal limit. By stacking these gatherings, one could have as many attendees as possible. In the case of my state, an hour event could support 40 people which is larger than most events locally. For state rules it would be separate events. For geocaching it would be one event. How are folks handling this?

It is nice that things are back to normal. I learned somethings about the existing trust hierarchy today. It is more fragile that expected.

With different security settings and network caching some people seem to not be having problems. It has not hit the apps on my android device. cachetur.no seems to be able to pull from the API. Commentary on facebook seems to suggest it is an expired certificate somewhere.

gsak users are complaining about authentication issues on their forum and on facebook. Project-gc.com is also having problems as well and posted on facebook about it. It appears to have happened around 7AM ET.

This still seems to be an issue for me.

Howdy, http://status.geocaching.com seems to work fine but https://status.geocaching.com is reporting security issues for me in firefox, edge, and chrome. Is anyone else having this issue? Thanks.

this issue appears back for Version 8.18.2 Android 10 samsung SM-G975U Logging out, clearing cache and clearing data did not help.

Still an issue with. ]Version 8.18.2 Android 10 samsung SM-G975U

This may be related. I recently (yesterday) cleared the cache and data on my mobile to solve a draft problem. None of my souvenirs have downloaded since then.

After a recent chat with my local reviewer, I cannot publish an event for a day after the current department of health guidelines expire because of events are not being published within the current order. This will lead to a gap after the order expires where there cannot be events that are not published after the order started. The simplest is an event that occurs the day after the current order. The CO needs to submit it 2 weeks ahead of time and the reviewer has 7 days to react. Anywhere in the 7 day window after the lifting of the order will not be possible to have one's event published. Given that this is a few weeks away, is there any action to improve the software so that events can be approved but not published. They could then be published automatically within say 24 or 48 hours of the scheduled expiration of the order. This would afford the governments the opportunity to extend the order and also allow the geocaching community to return to normalcy sooner without the gap.

Howdy, Is this why I can no longer enter a URL for a background image? While I understand the privacy stuff and the need to enforce it with the proxy, why does this need to change my workflow?

Does anyone have an android or PC app that they like for poor connectivity environments? In particular I am thinking about opportunistic caching as opposed to planned trips. This would cover new caches being published in the area. Unexpected road detours make preloaded lists incomplete. Unexpected errands and DNFS also sometime trigger this behavior. Unexpected flight delays/reroutes may fall into this bin. In particular the hilly environments of Vermont come to mind for me as an example where phone coverage drops in and out. At a road crest the connectivity can be great. Speeds can be faster than a pocket query download can saturate. But off the crest connectivity quickly drops off to zero. Similar things can happen when around libraries or other public wifi. What this means technically I am not sure. The following are a quick list that comes to mind. Automatic retries for disconnects. Aggressive monitoring of network connections Smart API usage to get maximum information with minimal delay/throughput Smart caching (computer science sense) so data doesn't need to be Wider radius for live mapping Smart use of multiple parallel https connections (The 6000/IP address limit) Smart use of keep alive to reduce connection times. Queuing between different types of API calls to keep things flowing with the 60 calls per minute per call type. Perhaps some tracking missed calls so data can be managed/fetched for the next trip through the area. Spatially aware API usage that try to be predictive of data needed. Perhaps interfacing with a routing app. (Cache along route like) Proxy server component to improve throughput/buffer fetches when disconnected. How to do any of this and remain compliant with the licenses and quotas remains as they say an exercise for the reader. My hope is to get away from needing to preload large databases for difficult environments and still have the responsiveness of a connected environment.