The second video kind of changes the brightness.. but it also changes the color :)

Love the Oceans 11 spoof!

Hey tomasien, I've thought about making this into a service but haven't had time working on my current startup. In the mean time there are some folks that are solving the same problem check them out http://flavors.me/

Agreed! Will do! Thanks for the suggestion!

Due to the unexpected number of hits... Twitter is rate limiting the requests per hour... So instead of doing nothing it redirects to twitter...

Thats really smart. Maybe edit that into the blog post for now, otherwise people are going to be confused and submit bug reports (like i was going to).

I guess caching is in order

Aha .. smart default!

Maybe you should make a Node.js fork... I was thinking about doing one myself!

Wintersmith and Blacksmith are both Node alternatives.

Issue fixed. Please let me know if you find any more issues, or create an issue in github. Thanks!!

Thanks for taking care of this! I like what you're doing with this. As a Tumblr-head, I think you should also consider adding follow, like and reblog functionality. The API also has functions for this.

But either way, I'll be keeping an eye on this!

I fixed this issue just haven't pushed to rigoneri.com yet.. Thanks!!

Fix deployed! Thanks again!

I dont think so. Im using hackernews app on iOS,which displays your page truncated and unusable. Responsive means all widths are possible, not just some of the more common ones.

Related, on http://rigoneri.github.com/syte/, down the page where it talks it about Responsive, it shows two images side-by-side.

One is clearly an example of responsive on a phone or tablet, but the other appears to be an example of broken responsive where the content got truncated as the OP of this thread mentions?

Why show an example of broken responsive design?

I don't know what this fix included but I can't see part of the text in my browser (about 1100 width). There should probably be some margin on the right side as well so text doesn't touch the border (or overflow).

Great catch, I'll fix it... The reason is that it uses the same URL for a regular HTTP request and a XMLHttpRequest...

Why did you build it that way instead of having a specific API path?

Good point. The reason was so I can swap from Django to Node easily if I wanted to without to much work and so the page can load faster on first request... I can probably change that eventually or just wait for a pull request :)