Erik Bjäreholt

This is problematic due to the start and end of a "day" not being well defined because of timezones. One could imagine summarizing over each hour-period, but I'd really like...

@nicolae-stroncea That is true, and we've thought about that before. But as long-term analysis is considered to be a rarely-used function it's not a priority. You described the solution well...

@nicolae-stroncea Glad to hear it! Keep us posted.

We're aware of this unfortunate behavior (it's been discussed elsewhere, can't remember where though) and there's actually a fix in the works with the new sqlite datastore @johan-bjareholt has been...

It should be a really easy fix though, I think we just need to call set `treaded=False` somewhere: https://stackoverflow.com/questions/38876721/handle-flask-requests-concurrently-with-threaded-true

@jantman I've seen it but that's likely a lot more work. Since we've so strongly decoupled our database logic from Flask there's not really a clean way to create a...

A more pragmatic solution might be to write an importer tool.

**An option to using the Wakatime API:** Wakatime stores a file `~/.wakatime.db` which contains a SQLite store with not-yet sent heartbeats. Maybe disable sending of them via `~/.wakatime.cfg` and hopefully...

Because it is still the reference implementation, and faster to prototype stuff in.

Because I wanted it to follow the coding conventions of the flask-restplus example projects, which will make it easier for me to follow the examples [here](https://github.com/blohinn/flask-restplus-full-todo-example-with-jwt) (JWT) and [here](https://github.com/frol/flask-restplus-server-example) (OAuth2)...