As a frontend developer, when I want to try a new framework, I want to do something a little more elaborate than the todo-list that everybody has already done hundreds of times … What’s missing about that is data.
This is what topheman-apis-proxy is about : it gives you access to public APIs to get data to feed on and not have to bother about the server-side, focus on the client-side – install once, configure your credentials and you’re good to go.
You can currently access to the public APIs of Twitter and Github. I’ll add more and you’re welcome to get involved. You can configure things like CORS, access by token …
It is based on expressJS, I already use it for one of my projects.
If you’re a developer I assume you’ll jump right to the readme on github 😉
With the Twitter Stream API, you can only open one stream at a time, so if you want to track different kinds of keywords (aka channels), all the tweets in result will be mixed up and you’ll need to do some post-processing to identify which tweet belongs to which channels.
I needed that kind of feature for my next project, so I decided to make a module out of it. Feel free to use it. Some infos you might be interested in :
- The API documentation (generated from source code with yuidoc)
- The github repo (with the README)
- twitter-stream-channels on npm –
npm install twitter-stream-channels
- The module has a complete built-in mock version accessible via
.getMockedClass() that will let you use it without connecting to Twitter (usefull because of their connexion limit)
- It also is unit-tested, if you want to contribute (first time I made unit-tests on node with mocked data dispatched by events – by the way, I improved test’s speed using
process.nextTick instead of
setTimeout in mocked mode).
I’m currently working on a project based on twitter-stream-channels that I wil release in a few weeks.
edit : I just released the project I was talking about. More about it on this post.