search

CuppaZee / Legacy

Legacy Version of an app to support players of the geolocation game Munzee.
https://cuppazee.app/
Mozilla Public License 2.0
9 stars 4 forks source link

Weekly/Monthly and maybe alltime Stats #76

Open Megachip opened 4 years ago

Megachip commented 4 years ago

Is your feature request related to a problem? Please describe. Nope ;) Would like to see long term stats similar to the one day stats in MunzStat or like gc_stat/oc_stat generates for geocaching. These could include:

Describe the solution you'd like To prevent additional load to the api, the data of older days could be stored persistent on the phone and only refreshed on request (e.g. lately submitted offline caps)

Describe alternatives you've considered Doing API requests for a longer period of time isn't a good alternative :(

Additional context Provided on request. Hopefully Explanation is enough ;)

Megachip commented 4 years ago

oh, figured out, that at least all time already exists ;) https://statzee.munzee.com/player/leaderboard/

sohcah commented 4 years ago

This would use a lot of API requests. Assuming I could designate 10 requests per minute for fetching this data, it would take over 4 hours just to fetch this data for my account. So, unfortunately, this probably won't be possible. 😢

Megachip commented 4 years ago

This would use a lot of API requests. Assuming I could designate 10 requests per minute for fetching this data, it would take over 4 hours just to fetch this data for my account. So, unfortunately, this probably won't be possible. 😢

Thats why the described solution. Just cache/store the data, the user already requested. So its up on the user to keep his local backup/copy up2date. Everything else would kill the servers ;) ... Ill guess we saw the result when the first universal was released ;)

Lets keep it as an idea, if you're fine with it ;)

Maybe some times someone will find the time and resources ;)

sohcah commented 4 years ago

Unfortunately, it would still take 4 hours that first time.. for a single person. Any other people that want to use it would have to wait for that 4 hours to be over to use it themselves. If you had even 12 people wanting to use it, it would take 2 days to load for them all.

sohcah commented 4 years ago

Sure, it may only take a minute or 2 for future loads, but with 2491 CuppaZee users, it's completely unfeasible.

Megachip commented 4 years ago

I do not plan any additional api requests ...

I'll guess, not yet checked, why my profile is loaded, the data for the actual day will be loaded (what did I cap, who capped things from me... including types, points etc) ... when I change the day, these data will be loaded for that day. So, why not just store these data persistent and generate stats out of this local data? - maybe there is data missing cause the user didn't opened that date...

sohcah commented 4 years ago

We wouldn't have that data cached from the past. Some people have been playing this game for over 9 years now.. so going back and getting data for every single day going back would take a huge amount of time.

sohcah commented 4 years ago

If this were possible, I'd implement it, definitely. But due to the Munzee API having strict limits on the amount of API requests I can send, it's really not possible. 😢

Megachip commented 4 years ago

We wouldn't have that data cached from the past. Some people have been playing this game for over 9 years now.. so going back and getting data for every single day going back would take a huge amount of time.

They have to this either manually day by day (congrats ^^) or living without that data. There should no automatism which increases the load to the api.

For the moment it's just an idea, which I didn't want to loose out of my mind. No priorities or anything.