You could add that obviously, but since we have already decided to have host specific buckets this is not the case. The aw-webui also currently uses the bucket hostname to identify which buckets to match, so it would be pretty annoying to have a corner case for this watcher.
This gives the exact same functionality anyway. Our database is also optimized to fetch events from a bucket so this would make it much slower in the case where you only want events from a specific host (the “data” field is just a string, would have to go through that data manually).
It would be preferable to only send the active ones.
We had a similar scenario when developing aw-watcher-window where the most important functionality was to send the focused window but we also considered sending which other windows were open in the background. We decided to have one bucket with the eventtype “currentwindow” which contains the focused window and then considered having a separate bucket with the eventtype “allwindows” or something like that, but then realized that there’s little use of tracking windows which the user doesn’t use. After all, what’s interesting with activitywatch data is what programs you are using the most, what programs are running but you are not using are generally not very interesting data.