[00:25:51] Analytics-Kanban: Communicate the WikimediaBot convention {hawk} [5 pts] - https://phabricator.wikimedia.org/T108599#2024713 (jayvdb) I see that the user-agent policy was updated by an IP address. https://meta.wikimedia.org/w/index.php?title=Talk:User-Agent_policy&diff=prev&oldid=15344621 Is wikitech-l going... [02:01:35] Analytics-Kanban: Dedicated and/or automated Wikimedia pageviews API project/tag in Phabricator Maniphest [1 pts] - https://phabricator.wikimedia.org/T119151#2024838 (madhuvishy) https://phabricator.wikimedia.org/tag/pageviews-api/ is created! [19:06:55] hello, I assume everyone is away for the weekend? I have a few questions about the pageviews API [19:11:31] MusikAnimal: https://wikitech.wikimedia.org/wiki/Analytics/PageviewAPI [19:12:22] well, I specifically wanted to ask about the high-volume access [19:13:09] I'm developing https://tools.wmflabs.org/pageviews and want to implement a "mass query" feature. My hope is simple throttling will get around API limitations [19:13:40] but the part about "set a unique user-agent header so we can contact you" worries me. That obviously doesn't apply here as it is a frontend application [19:15:03] I figure I'll throttle it to no more than 300 requests per second, well below the stated 500/s limitation. Hopefully then there won't be any concerns raised by WMF [19:17:22] I don't believe there will be many "mass queries" anyway, but I should be prepared. It's a frontend app, they could just keep hitting refresh, open in a new browser, etc, and the app wouldn't be able to throttle properly [20:59:19] Quarry: Include query execution time - https://phabricator.wikimedia.org/T126888#2025894 (Slaporte) NEW [21:07:58] Quarry: Include query execution time - https://phabricator.wikimedia.org/T126888#2025903 (mahmoud) +1 ! :)