Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update on issue of aw-watcher-web reporting unknown hostname #132

Open
DivineMK opened this issue Aug 25, 2024 · 5 comments · May be fixed by #143
Open

Update on issue of aw-watcher-web reporting unknown hostname #132

DivineMK opened this issue Aug 25, 2024 · 5 comments · May be fixed by #143

Comments

@DivineMK
Copy link

I come from #67 and see that the issue is closed already as OP main issue was resolved, so I want to track this specific issue again.

The issue is with buckets from aw-watcher-web having "unknown" as hostname.
@losogudok
Copy link

Workaround I found:

  1. Build extension according to README
  2. Change hostname "unknown" to your computer hostname and PORT to 5600 (dev version uses 5666)
  3. Load extension to Chrome (dont forget to enable dev mode)
  4. Enjoy!

@soqb
Copy link

soqb commented Oct 9, 2024

that doesn't work on firefox. the default release channel doesn't let you use unsigned addons.

@Cyber5imon
Copy link

Here are the basic steps to sign your own custom Firefox add-on:

  1. Get the credentials from AMO.
  2. Download and Install NodeJs.
  3. Install web-ext using this command: npm install --global web-ext
  4. Go to your add-on directory.
  5. Run this command: web-ext sign --api-key="JWT issuer" --api-secret="JWT secret"
  6. A folder named "web-ext-artifacts" is created containing your signed XPI file ready to be installed!

@DivineMK
Copy link
Author

Thank you for sharing the workaround. I will keep the issue open until this can be integrated into the extension as an option.

@Thunder33345 Thunder33345 mentioned this issue Nov 14, 2024
Open
@simonmysun
Copy link

I wonder if it would be better to add a optional input on https://github.com/ActivityWatch/aw-watcher-web/blob/e2cc98c3ac02cba86f8ee2d7141f71d47ebcacc0/static/popup.html

kepstin added a commit to kepstin/aw-watcher-web that referenced this issue Dec 4, 2024
@kepstin
Allow manually configuring the hostname
507b63c 
Without any obvious ability for the extension to determine the machine's
hostname automatically, the best available option seems to be to allow
users to configure it manually. A field is added to the extension popup
to configure the hostname.

The field is blank by default, and the updates were designed to ensure
that the behaviour if the hostname is not set will be unchanged (so
people using workflows that expect browser data in the "unknown" host
bucket won't see anything break; they can set the hostname once they're
prepared to do so).

Fixes ActivityWatch#132
kepstin added a commit to kepstin/aw-watcher-web that referenced this issue Dec 4, 2024
@kepstin
Allow manually configuring the hostname
a63d53b 
Without any obvious ability for the extension to determine the machine's
hostname automatically, the best available option seems to be to allow
users to configure it manually. A field is added to the extension popup
to configure the hostname.

The field is blank by default, and the updates were designed to ensure
that the behaviour if the hostname is not set will be unchanged (so
people using workflows that expect browser data in the "unknown" host
bucket won't see anything break; they can set the hostname once they're
prepared to do so).

Fixes ActivityWatch#132
kepstin added a commit to kepstin/aw-watcher-web that referenced this issue Dec 4, 2024
@kepstin
Allow manually configuring the hostname
3bcbc9a 
Without any obvious ability for the extension to determine the machine's
hostname automatically, the best available option seems to be to allow
users to configure it manually. A field is added to the extension popup
to configure the hostname.

The field is blank by default, and the updates were designed to ensure
that the behaviour if the hostname is not set will be unchanged (so
people using workflows that expect browser data in the "unknown" host
bucket won't see anything break; they can set the hostname once they're
prepared to do so).

Fixes ActivityWatch#132
kepstin added a commit to kepstin/aw-watcher-web that referenced this issue Dec 4, 2024
@kepstin
Allow manually configuring the hostname
53e1345 
Without any obvious ability for the extension to determine the machine's
hostname automatically, the best available option seems to be to allow
users to configure it manually. A field is added to the extension popup
to configure the hostname.

The field is blank by default, and the updates were designed to ensure
that the behaviour if the hostname is not set will be unchanged (so
people using workflows that expect browser data in the "unknown" host
bucket won't see anything break; they can set the hostname once they're
prepared to do so).

Fixes ActivityWatch#132
@kepstin kepstin linked a pull request Dec 4, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow manually configuring the hostname kepstin/aw-watcher-web
5 participants
@Cyber5imon @simonmysun @losogudok @DivineMK @soqb