Johan Bjäreholt

> I added the firefox web watcher a few hours ago, but there is no data in the aw-watcher-web-firefox bucket. So the bucket is created but there is no data...

``` sources: TypeError: can't access dead object ``` Aha. It's most likely that for some reason your browser is quick at dropping the info about the tabs which aw-watcher-web has...

I have had a similar issue now actually, but it did not occur at all at when I expected it to. I was testing the aw-server-rust server instead of the...

If you have the time to debug, please try out the aw-watcher-web branch in #33 and look at the console, should hopefully provide better error messages

I'll close this, have not seen the issue in a very long time.

A user on the forum reported that this might be because of a setting in firefox https://forum.activitywatch.net/t/unable-to-connect-to-server-with-aw-watcher-web-firefox This should be documented!

> However, for Android apps it's still an improvement (since I assume they can't snoop on local packets however they like). Aha, that makes sense.

Seems very strange to always have to point out a remote binary for aw-server, wouldn't that be quite annoying if you had to test changes in aw-server-rust with it?

> When I used to wait maybe 30-40 seconds for a monthly review, it now takes 10 seconds. Still 10 seconds? Sounds like we still have room for improvement ;)...

About the DB size that could also simply be because of database fragmentation. If you import everything in order afterwards there will be less fragmentation.