UPDATE: I have applied to Twitter to have C:SI white-listed so that they are not subject to the API Request limit, and was just now notified that the request was approved and will be in effect within 48 hours.
Every once in a while I guess I just get a bizarre notion in my head and have to see if it works. Today’s case in point: Twitter.
A lot of the people in my industry whose blogs I follow seem to mention Twitter in nearly every blog post. I’ve never really understood why so many people find Twitter so compelling, and I sometimes whether I will some day have the epiphany and finally get it, or whether everyone else will eventually realize that it’s really not much more than "technology for techology’s sake".
But in any case, I’ve seen a lot of buzz about social networking API’s, and Twitter’s API is commonly mentioned in that regard, so I thought I’d take a look at it and see how complex it is.
Well, I guess it couldn’t really be easier. To post a message to Twitter is a matter of a very simple HTTP POST request. Easy-peezy.
But, I don’t really have anything to post about. Nobody wants to hear about my boring old life, so as I was sitting there desperately trying to think of *some* use for this kind of service, I realized that I could very easily post the results of every C:SI duel in real time, and even do so without causing the existing C:SI back-end to even so much as breathe hard.
It’s true. Go to the @CombatSI Twitter Feed to see what I mean.
Now, this was not approved by anyone else, and it may even turn out that there will be some people who hate the idea, so keep in mind that I may pull the plug on this at any time without any warning or reasons given.
I just thought it was an interesting exercise, and maybe a few people will think it’s kind of cool. Isn’t that what skunkworks is all about?
9 Comments
Does the fact that there are a clean 500 updates and no new updates in an hour mean you’ve hit some sort of daily limit on API usage?
Yes, yes it does
Sheesh. The limit it hit was 100 API requests per hour. Wow, that’s low. Especially given the amount of activity in the C:SI community
I’ve applied for whitelisting, but I don’t know if there’s even a chance of that. Failing that, well, I guess I will just trash the whole idea and come up with something else.
I’ve learned some very interesting things in this process, and will be always looking for ways to incorporate that in future C:SI features and updates.
Apparently, once you hit that limit, you are blocked for 24 hours.
So, yeah… Okay…
I think the right thing to do is say “Screw Twitter” and trashcan the project
I have applied to Twitter to have C:SI white-listed so that they are not subject to the API Request limit, and was just now notified that the request was approved and will be in effect within 48 hours.
so what’s interesting is that not all of the duels are reported on twitter even today. I sparred a good friend today and although her wins on me were listed, mine on her were not, even as her total wins/losses reflected my wins on her. Just an observation.
Really?!?!??!?! I wonder why that is?
I will look into that!
We had a battle in Penghu today. Quite a few deaths were not registered. This was basically a huge team vs team FFA. Curiouser and curiouser?
Hmmmm… I wonder… Is it possible that this is weapon-specific?
I suppose that’s possible, and is something I should look into.
I just made some changes that could perhaps result in better coverage? I won’t be able to get in-world to test this stuff until later, but it seems logical that what I just did could have had a positive effect.