Multiple web watcher buckets per instance broken due to hostname unknown

[ErikBjare]

Hostnames of web watcher buckets are always "unknown" which breaks the activity view when multiple such buckets are present (it will just pick any browser bucket since it can't filter by hostname due to the hostname being "unknown").

We should:

• Make the client use the hostname given by the /api/0/info endpoint as the bucket hostname. (or build a way for the server to automatically assign a hostname, but that seems unnecessary)
  • This is easy
• Upgrade existing buckets somehow
  • This is harder

There is also a host of related problems since we (it was probably me) made the terrible decision of using hostnames as device identifiers, see #302 where we're discussing fixing that.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mindflowgo]

I get this error on Mac, using Brave browser, 30 minutes after install:

Unable to find bucket matching 'aw-watcher-window_unknown' (hostname filter set to 'None')

Either Visual Code or Brave or Terminal would have come us unknown host on my Mac.