Page MenuHomePhabricator

feedrecentchanges days is too coarse
Closed, DeclinedPublic

Description

feedrecentchanges days is too coarse. Please also add a seconds parameter.
(From the viewpoint of seconds, you only allow 86400, 172800... seconds.)
Motivation: a cronjob that checks this daily
26 22 * * * GET http://radioscanningtw.jidanni.org/api.php?action=feedrecentchanges&days=1 |sed '1,/<item>/d'
but one worries about not giving it a few more minutes overlap day to day.

Also allow time frames, like UNIX find -mmin +22, -mmin -44.

list=recentchanges already could do this.

Event Timeline

Jidanni raised the priority of this task from to Needs Triage.
Jidanni updated the task description. (Show Details)
Jidanni added a project: MediaWiki-API.
Jidanni added a subscriber: Jidanni.
Jidanni triaged this task as Lowest priority.Mar 25 2015, 11:44 PM
Jidanni updated the task description. (Show Details)
Jidanni set Security to None.
Anomie claimed this task.
Anomie added a subscriber: Anomie.

feedrecentchanges doesn't actually handle the 'days' parameter, it calls into SpecialRecentchanges or SpecialRecentchangeslinked which processes the parameters. That sucks, but it's the way it is.

Also, it appears the 'days' parameter as handled by SpecialRecentchanges goes to the day boundary, e.g. days=1 starts at 00:00:00 UTC yesterday rather than 86400 seconds ago. Further, if you want a specific starting time you can use the 'from' parameter instead.

  1. Nobody would have ever guessed this is the case.
  2. Be sure this is all documented there offline.
  3. Using firefox http://radioscanningtw.jidanni.org/api.php?action=feedrecentchanges&days=6&from=2015-03-23T23:54:55Z and varying the days parameter shows in fact that "from" is indeed totally ignored anyway!
This comment was removed by Jidanni.