Personally, I'd love to see this working without having to send data to the Koala servers. My job has some strict policies on what data can be send to third party servers and I'm not sure how this relates to project/client names/details. I imagine others are in the same boat.<p>I believe it would be relatively simple to calculate time locally and then display the totals in some custom Atom buffers.
> We invented a /new/ time tracking system..<p>Having had a very quick browse on the page. This looks like wakatime.com.<p>I've been using that one for a couple of months with zero problems, it gives me an very detailed overview of what I worked on (down to filename, h:m:s editing, git branch name etc) and it gives me daily and weekly summaries.<p>Is there a reason for me to change to koala?
Some website quirks I noticed:<p>- When I go to pledge/api docs I see previously hidden navbar links 'events', 'reports'<p>- If I enter the 'events' section, it asks me to sign in and the browser history back action stops working.<p>I'm really impressed by the pledge you're making there, it's a very amicable touch.