Laurent Eschenauer

Git is not easy. Picking the right Git workflow for a collaborative open source project is even harder. I have tried many, and always found limitations that turned the repo into a bazaar. I like this one, it is complex but complete. The trick is to keep the hotfixes in their own branches and to always bump the release number when pushing to master.

What about you ? Any other Git workflow/tutorial to share ?

"More than half of the internet’s top websites use a little known capability of Adobe’s Flash plug-in to track users and store information about them, but only four of them mention the so-called Flash Cookies in their privacy policies, UC Berkeley researchers reported Monday.

Unlike traditional browser cookies, Flash cookies are relatively unknown to web users, and they are not controlled through the cookie privacy controls in a browser. That means even if a user thinks they have cleared their computer of tracking objects, they most likely have not."

A must read if you are into node.js, or interested by scaling web services in general. Some very good points on the challenges of 'scaling in the large' and by large, we mean thousands of servers to power your gazillions of users.