pindi

6 ms·

31.
by pindi 14y ago
A great initiative from a great team.
32.
by pindi 14y ago
For anonymous users, generate a random token and store it in a cookie. Or you can use the IP address as nivla suggested. Yes, at with these techniques you're tracking users across requests. But that's the point of this kind of analytics, is
33.
by pindi 14y ago
The tokens are cryptographically signed with a shared secret between the main server and analytics server. So an attacker can't forge another user's token. IP addresses would be a good solution also, especially if you need to track anonymou
34.
by pindi 14y ago
I often have the same concern. What I ended up doing was issuing a token to each user, and verifying the token on the logging endpoint. That way, if someone decided to fill the logs with spam, we can easily delete all the events from that t
35.
by pindi 14y ago
I really like this tutorial's format. I made another one in its spirit about Agility.js, another framework that is significantly more succinct: http://www.pindi.us/blog/step-by-step-from-jquery-to-agility...
36.
Step by step from jQuery to Agility.js(pindi.us)
2 points by pindi 14y ago|0 comments
37.
by pindi 14y ago
Sure, in some cases it makes sense to make the tradeoff of not handling more obscure characters. But if the tradeoff is made, the encoding should not be called UTF-8. "UTF-8 (UCS Transformation Format—8-bit[1]) is a variable-width encoding
38.
by pindi 14y ago
I don't think there's a "right way", but I prefer the second format. In the first format, it's difficult to delete and recreate the entire virtualenv without also deleting your project files. And in the third, your environments are unnecess