their analytics service still won't work since Github's camo proxy scrubs all cookies, referers, remote addrs, etc. edit: and regarding lua or nginx redis2, ye

their analytics service still won't work since Github's camo proxy scrubs all cookies, referers, remote addrs, etc. edit: and regarding lua or nginx redis2, yes you could certainly do that. I happen to like the asynchronous nature of incrementing hit counters outside of the request cycle and just using nginx to serve the static badge files. But yeah there are a bunch of ways to do this.