What To Do When Your Web Application Goes Viral
dlo.me
dlo.me
The yellow was distracting though, that made me think I had the browser's Find open.
Did you end up reading or getting a friend to do business-related? What was it like?
Nice write up. Congratulations on being successful!
I actually did go through a lot of them, but there were so many emails / outreaches that it was pretty much impossible to personally respond to everybody. I forwarded most of the emails to a few of my friends who actually did an amazing job of getting in touch and following up. Things have worked out pretty well so far :)
Phone calls especially are my weak point. A thirty minute conversation in the middle of the day is enough to destroy my productivity for an entire afternoon. So I tried to avoid as many of those as I possibly could.
If you're on your own server, you don't need to be running with the debug loglevel unless you really need it. But if you really need it, you won't be screwed: all you need to do is configure logrotate's size parameter to a reasonable value. Most logs compress very well.
On 5, I honestly would have thought your line of thinking was right before this fiasco, but the vast majority of my emails were not bug reports. Most bug reports came through Twitter and Uservoice (when I had it up).
I think the term of trade for "log everything", in the sense that you used it, is tracing.
Edit: Just committed. https://github.com/dlo/django-on-appengine
Aren't you open to the client lying to you, though? Requesting the information in the client and having it send it to the server gives you less of a guarantee of its validity than if you did it entirely in the server.
Actually cloudkick has a free plan, that works on one server only.