Gaps Weaknesses

From GotWiki

Here are some of the problems with my current approach. Some are gaps, others are weaknesses or shortcomings of conscious decisions that I've made.

For starters: My decision to clear my NotFound database in GSAK virtually every time I get a new PQ limits the amount of history I can build up for each cache. Without deleting them all, you would begin to develop a long-running chronology of log history. However, in my scenario, I will never have more logs for a cache than were delivered in my most recent PQ.

This is an understood trade-off - with the positive benefit of clearing out any archived or temporarily disabled caches (who needs to be bothered with them?). However, on extremely rare occasions, I find myself wanting to see more history for a particular cache - typically, one that I can't find. That's when the Blackberry (or iPhone, if that AT&T network weren't so darn slow) comes in handy.

Another gap is my lack of DNF tracking. While I use CacheMate to record my DNFs - I've yet to build the macros and develop the associated processes to import them and help automate the logging of them. This would be good - as right now, I do a pretty haphazard job of logging my DNFs. Then - even for the ones I do happen to log - I don't track them in any way (though if I log them online, the do end up represented in GSAK, whether as logs for caches I eventually found, or ones I still haven't). That is - assuming I'm tracking that cache (e.g. it's somewhere 'local'). However, DNFs from distant areas (e.g. Europe, Florida - places where I don't routinely pull PocketQueries) are just 'lost'. I'd like to build, and maintain, a DNF database in GSAK.

I'm sure there are others - but these are the primary items that come to mind.

Back to Paperless Caching