opencaching / opencaching-pl

The source code of Opencaching.PL (and some other domains)
https://opencaching.pl/
GNU General Public License v3.0
22 stars 33 forks source link

A list of most recently visited caches #2176

Open rapotek opened 4 years ago

rapotek commented 4 years ago

It is a proposition of a "nice-to-have" feature, introducing a list of most recently visited caches:

The feature in theory could reuse existing CacheVisits BUT: the latter registers only unique visits (one per week for given cache and user), while here every visit should be registered. Moreover, the manual removal could be problematic here due to count computing dependencies. Therefore I recommend using a separate solution, regardless of a storage space redundancy.

kojoty commented 3 years ago

@rapotek technically it can be done but I can't see the reason to implement it - what is a user scenario for this?

User opens the map and look at geocaches and want to come back to viewed geocache? for what? I have never needed such option and can't imagine who needs it and why (of course I can be wrong).

rapotek commented 3 years ago

And I use it very often on GC, where there is such a list, but with limited functionality (without a "manual" removal f.ex.). I like to return to listings of caches which have attracted my interest because of some reason, but without adding them to the watchlist or clipboard. It is a kind of a nice-to-have feature, to see my "visits" history for example. But if you don't see the need to implement this, I can gladly close the issue and use clipboard instead, although I have to remind myself to add a cache to it when visited.

PS: Does every user have to start looking for caches from "opening the map"? Caches' pages entries directly from "My Neighbourhood" are not so rare in my case, for example.

kojoty commented 3 years ago

But if you don't see the need to implement this, I can gladly close the issue..

@rapotek - please - we all can decide what we want and what is not necessary - I just wanted to understand the idea

there are features which we MUST find consensus because they are crucial for OC and there are ideas (like this) which can be an option for node and for users as well - so if you want to spend time to implement it - it's just your choice :) and I believe everyone have nothing against such initiatives