7 ms·
I agree about lowering the question frequency. It's high right now so I can find bugs faster. Stability is key to me. I don't agree about making it on US time,
by timdorr 18y ago
I agree about lowering the question frequency. It's high right now so I can find bugs faster. Stability is key to me. I don't agree about making it on US time, though. Twitter is a very international service, so giving an advantage to one side of the planet would be no good.
I'm figuring a DM versus a tweet for responses. If this gets popular (even minorly so), it's going to drive up the noise like crazy if the @playtwivia stream is nothing but answer responses. I'm actually waiting on the Twitter team to raise my API limit so I can implement that.
- jackowayed 18y agoThat's true. You're right, definitely d's. And yes, I definitely agree w/ your todo list that you need a way to allow several answers or something. Just wondering, what's it written in?
- timdorr 18y agoQuick and dirty PHP. In fact, the most complex part of it was piping emails for the direct messages into PHP. I hadn't ever done anything like that, but it's useful to know.
- jackowayed 18y agoalso, you shouldn't need them to raise your rate limit for that. From Twitter API Wiki (http://apiwiki.twitter.com/REST+API+Documentation#RateLimiting http://apiwiki.twitter.com/REST+API+Documentation#RateLimiti...): POST requests (ex: updating status, sending a direct message) do not count against the rate limit, but some actions may have caps on them to prevent abuse. So in the long run you may need it so that you won't hit those caps, but it shouldn't count towards your 100/hr.
- timdorr 18y agoAh, thank you. I'm thick and missed that. :)