-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
downloads counting system #109
Comments
Another option: Downloads per dayIf the primary concern is that old mods have an advantage over equally good newer mods, we could determine the date of the first release of a mod and then divide the total downloads by the number of days that have elapsed since that date. Examples
(Data current as of this writing) Pros
Cons
|
I like Downloads per day and it looks easier than Last time-period and better than All downloads. But we still have problem with the first — downloads on the last months/releases more important for popularity than downloads years ago.
I think good idea is to start with Downloads per day (user could switch between this and total downloads), but also to save downloads every day on a different files. Then, after a month, to change default downloads per day to downloads per day on the last month (same thing as Last time-period) and to leave user possibility to switch to other two counting. |
SomeDiscoveries while looking for web hook callers in source code... While SD doesn't have upload date or a granular download count in its main API pages, both are available elsewhere via specially formatted URLs:
|
Some problems with getting upload date from all rss feeds? |
Why? The chart doesn't show 'used to be' time interval. In the last 2 years 80k US2 vs 40k US1 — 2x difference; even larger difference for the last year |
300000/80000 = 3.75, 300000/40000 = 7.5. |
The game itself could become less popular, that entails new mods been outpaced by the old mods by raw downloads count |
Yes, that's one possible explanation. |
All_downloads counting
Now downloads in GUI is a sum of all downloads for every released version.
pros:
cons:
We can't really compare popularity of 2 mods — age of mods and counts of mods' updates have large influence to all_downloads (but not to popularity)
enormous latency — for a new mod to be qualified as popular is not about quality, but about how long the mod will bouncing around
Last versions counting
Another way to measure popularity is to count not all_downloads, but last_version_downloads, or, even better, maximum of 2 last versions downloads.
pros:
cons:
UPD
Last time-period counting
On the NetKAN-bot side save all_downloads values every day in a separate file and calculate downloads for the last week or month or few month as difference of numbers in corresponding files, and maybe allow users to switch that.
One still can spam a new version every day for "popularity", but is fixes enormous latency problem, and do not require any API changes.
The text was updated successfully, but these errors were encountered: