Skip to main content

Why I wrote node-twitchtv, a NodeJS client for TwitchTV API

I use twitch.tv daily -- some of the main gamers I follow are nl_kripp, kungentv, kingkongor, and reckful. They're really . The mission is simple for Twitch: connect gamers with their audiences, anywhere and anytime. It is open sourced on Github and can easily be integrated into your existing NodeJS solutions by using "npm install node-twitchtv".

After searching on npm for a TwitchTV / NodeJS client, it seemed like no one has attempted this. I decided to take the deep dive and give it a shot. In part of the design for this module,

Round 1: Retrieving basic data like games, channel streams, users

Round 2: Authentication with OAuth2 (server-side workflow)

Round 3: Video streaming as easy as "npm install node-twitchtv" (once the APIs are open)


Where I was going with this: NodeJS runs on all platforms now, it even runs flawlessly on Microsoft's new Windows 8 operating system (which uses the same tools for Tablets and PCs). My heroic vision was, If you wanted to build a streaming client, it would be as simple as, "npm install node-twitchtv", write a UI over top of it, plugin your Oauth2 credentials and off you go (use the Windows 8 APIs like screen recording and pipe it into the client's listener).

As an example, it would be amazing to be able to easily stream your "Pirates and Daisies" (a very popular tablet/pc Windows 8 game) gameplay by simply enabling the permission for the node-twitchtv client emitter. The idea behind this is to empower the Gamer -- Gamers will change games over time and it's important to keep their loyal followers connected to them because it isn't so much the game that is bringing the value, it's the persona and level of expertise they bring to the game.

As part of moving this forward, I wanted to ensure that there was 100% engineering transparency. That means, taking in feedback from the community who were passionate about Twitch's mission and willing to move forward with its streaming APIs.
Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.

Cheers,
Jaime

World of Warcraft Ninjalist addon: version 0.1 coming along quite nicely

After toying around with more GUI related issues in World of Warcraft's API, I've decided to take a totally different direction. Originally when I architected this addon, I knew in my mind it would be a super simple Console application that a user could easily paste in a name and add it to the database; however, why stop there?

After discovering AceGUI, I can easily start developing UI components in no time! As of right now, I've got it saving data in between game sessions--the interesting part will come when I'll have to develop the web service that will parse the SavedVariable.lua, eliminate duplicate entries, as well as, do a huge merge between their copy and whats on the server's (per realm basis of course).

Here's a screen shot of the responses when adding new Ninjas to your list:
When a user clicks add after entering a name in the textbox, it'll go ahead and add that person to the ninjalist tagging the user's realm and current date/time. Someday, I…

Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:



Now, whenever you make a commit, it should show up like this in the log:



Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this



Want more emojis? check out the Emoji Mardown Cheatsheet!