Another small nitpicking (sorry if I become unnerving :P):
If I put ctshowagg=-0 in the URL (typo), the aggregates are shown. Without this parameter, the aggregates are not shown.
I would have expected that an invalid value for a parameter would make the script behave just as if the parameter didn't exist. Again, this is a very small thing and not a problem at all.
Thanks, Strainu "tooday I'm in QA mode"
2011/9/20 Nuno Tavares nuno.tavares@wikimedia.pt:
Strainu, the tools were focused on the participant's relevancy. I can imagine them (actually, I know they're doing it) participants hitting browser reload button a lot, so they see their uploads reflected in the stats.
The chart is not that relevant for a participant.
As a side-note, the charts are agressively more cached in a factor of 60 (5h) :-)
-- Nuno Tavares Wikimedia Portugal http://www.wikimedia.pt
Imagine um mundo onde é dada a qualquer pessoa a possibilidade de ter livre acesso ao somatório de todo o conhecimento humano. É isso o que estamos a fazer.
Participe também: http://www.wikimedia.pt
Em 20-09-2011 08:58, Strainu escreveu:
2011/9/19 Nuno Tavares nuno.tavares@wikimedia.pt:
Strainu, try adding &reload=1 to the end of the URL.
General disclaimer: Please do not abuse the system :)
Thanks Nuno, and don't worry, I only plan to use that trigger a few times a day to analyze the impact of my flickr-transfer bot on that day's uploads.
I was wondering: is the graph cache really more rarely updated than the api-bridge's one? It sure seems like it, but I find no obvious reason for that.
Thanks, Strainu
Wiki Loves Monuments mailing list WikiLovesMonuments@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments http://www.wikilovesmonuments.eu
Wiki Loves Monuments mailing list WikiLovesMonuments@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments http://www.wikilovesmonuments.eu