Johan Bjäreholt
Johan Bjäreholt
https://github.com/ActivityWatch/aw-server/issues/53#issuecomment-456445158 Good point, did a quick untested PR https://github.com/ActivityWatch/aw-server/pull/54
But this does not actually recover the old database right, only initializes a new one? To just get a new one, you can just delete the database while aw-server is...
That's very interesting, thanks for the tip! This should probably be documented in the official documentation somewhere.
Why are you working on refactoring aw-server-python when aw-server-rust has feature parity and will be replacing it?
But it's just refactorization, it doesn't add any functionality? Why spend time on refactoring something that we don't intend to keep for a longer period of time?
> I just discovered that aw-watcher-window already supports this feature, though not documented and only as a run-time argument instead of something in the configuration file. Oh right, I had...
IMO this would be best as a seperate module running in parallel with aw-server and the aw-watchers. It doesn't look to actually require to be inside aw-server?
> How long you need to engage in a 1 point activity to get 1 point? (an hour?) I never thought of it in that way at all. Since you...
Personally I wouldn't care about an auto refresh every 30s, especially considering that weekly/monthly queries are very demanding. Maybe if I have an activitywatch tab open which I go back...
This is an never ending issue, could we please split it into new separate issues such as "lowering bundle size" or "audit web-ui performance"?