[wp-meta] [Making WordPress.org] #1933: Automate Tagregator settings

Making WordPress.org noreply at wordpress.org
Fri Aug 26 13:45:45 UTC 2016

#1933: Automate Tagregator settings
 Reporter:  hlashbrooke                 |       Owner:  iandunn
     Type:  enhancement                 |      Status:  assigned
 Priority:  normal                      |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |
Changes (by iandunn):

 * keywords:  needs-patch => needs-patch good-first-bug
 * owner:   => iandunn
 * status:  new => assigned


 I think we should try setting up a set of default keys that all sites can
 use, but let them override it if they want.

 We'll need to double-check the API limits, but my rough worst-case
 calculations are that we'd have at most `14,400` requests per day in the
 short term, and `24,000` per day in the longish term.

 2 requests per min * 6 active sites  = 12 every minute = 14,400 per day
 2 requests per min * 10 active sites = 20 every minute = 24,000 per day

 Twitter's API allows `180` requests every 15 minutes, so we'd be fine
 there. (That's only for the Search endpoint; the others are `15` every 15
 minutes, but we don't use those).

 I'm assuming the other services have similar limits, but we should check.
 We could adjust the update interval if it's close enough.

 Worst case, if we did run into problems, organizers could always create
 their own keys to override the default ones.

 Also worth noting: Pinterest disable the API keys if the account connected
 to them doesn't use the app periodically, which is annoying and will bite
 us here. Maybe we just don't setup a default key for Pinterest, since it's
 break all the time anyway.

Ticket URL: <https://meta.trac.wordpress.org/ticket/1933#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list