As an API consumer I would like to request a list of articles that have been edited the most over a certain time period.
A/C
(Note this is essentially the same as https://trending.wmflabs.org/en/wiki/Special:Feed/enwiki/12 where 12 is a half life.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T140102 [EPIC] As a user, I want to see see a list of currently trending articles | |||
| Resolved | Jdlrobson | T145553 Subscription: Trending service should be able to subscribe to edits in real time | |||
| Resolved | Jdlrobson | T145571 Recovery: Trending service should be able to replay last 1hr of edits | |||
| Resolved | phuedx | T145554 Process: Trending service should process real time edits | |||
| Duplicate | None | T145572 Expose: Trending service should expose most edited based on a time period |
Currently the pages are exposed with limited filtering (we currently filter all pages which have had more than 6 edits)
Essentially this boils down to sorting and cutting the list of pages.
@Fjalapeno @bearND I'm going to need to understand how you want these filtered/sorted.
In Weekipedia
I filter to make sure there are at least 2 contributors and 100 bytes
I sort on a variety of factors (see link above) - weighting things based on the number of contributors, the bytes changed, the bias of the article.
Do we want me to sort in a similar fashion for this endpoint or would you prefer sorted by number of edits (of course your client can always do further filtering/sorting)?
We could also just filter these pages to things that meet a trend criteria (e.g. https://trending.wmflabs.org/wiki/Special:Feed/enwiki/n)
This means however that most of the time the endpoint would return an empty list.
It really depends on what you want to do with it...