Feature request: Allow multiple chrome browser with separate logs

[akademy]

I currently use Vivaldi with two profiles, one for work, one for home, but they both get recorded into a single ActivityWatch bucket. (You can install different extensions into each profile).

I would like to be able to customise the bucket name so that the recorded tabs I use are recorded separately.

(FYI, if anyone would like to do this themselves, find the app.js in the Extensions folder of your browser, and edit line 3329 (on version 0.4.3.0) to something else other than "aw-watcher-web-" + browserName.toLowerCase();)

Thanks for you work. 😄 👍

[Morpheus0x]

I am currently working on implementing this. The user will have the option to set a custom bucket ID from the extension popup. It would have been nice to automatically detect the profile name in Firefox and use that, but unfortunately this isn't the case. I am thinking of using a simple hash function on current time and use the first 6 digits as the default ID on install.

Edit: Using Enterprise Policy, the user can specify not to enable the watcher by default. This will allow for changing the bucket ID before it is registered, which prevents possible double bucket creation in ActivityWatch. However, I think this will only work in Firefox, a similar solution for Chrome would be nice. As far as I know, the equivalent of Firefox Enterprise Policy in Chrome doesn't provide a way to configure extensions.

Edit 2: Possible solution: just use the default bucket ID, without defaulting to a custom name with hash. The user can then choose after installation to change the default name.

[akademy]

Great work 👍

[Morpheus0x]

@akademy This pull request doesn't fix the issure raised here I just mentioned it, please reopen. I am currently working on a PR for this

[heroje]

It would have been nice to automatically detect the profile name in Firefox and use that, but unfortunately this isn't the case.
@Morpheus0x

I am not familiar with developing extensions, but it reminds me of how another extension handled recognition of Firefox profiles by running an external program:
https://github.com/null-dev/firefox-profile-switcher
https://github.com/null-dev/firefox-profile-switcher-connector

I hope this helps in some way. I'm running separate Firefox profiles at almost all times, and only one of them is able to record data in AW at this moment.

[paulirish]

(FYI, if anyone would like to do this themselves, find the app.js in the Extensions folder of your browser, and edit line 3329 (on version 0.4.3.0) to something else other than "aw-watcher-web-" + browserName.toLowerCase();)

This is the updated version that allows this to work:

diff --git a/manifest.json b/manifest.json
index 924e6a8..5096fe9 100644
--- a/manifest.json
+++ b/manifest.json
@@ -14,11 +14,7 @@
     "default_popup": "static/popup.html"
   },
 
+  "key": "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvXL8aewYb9SqcN84b8Ptw7BiSTPppTzsk/vrk6yzvuRITaU3O3nSNCWKLPVIMYk5Zz3MyXHmVFqFtfyM6CvwS+bCqR7iXMt+anFbqaW7y5yhzkxUN0IVGLCK5KJMPmCJ64rN8C4oG7FaeBQOKQX4VHCexWcBKfR2nUdV1czXJ3CrKuigD/6uEgvuXf2sKlvrPuaZqgjSmWQiPKjycmZrDuS1lxB9ThvPct3bOKNCikjnrCrvF6p86f6/q7p6ZitmGGZI/4qcRN9/3xC/pV0Ix8CTCwHUXyGaTlKvb9VFipj4x5DLacZB/JfWSJgxaerkGuLFD796oPITrbTqtif6PQIDAQAB",
 
   "background": {
     "scripts": [
diff --git a/src/client.js b/src/client.js
index 3a1fd6d..c8b2085 100644
--- a/src/client.js
+++ b/src/client.js
@@ -43,7 +43,8 @@ var client = {
     client.browserName = getBrowserName();
     // Check if in dev mode
     chrome.management.getSelf(function(info) {
-      client.testing = info.installType === "development";
+      // Despite loading as unpacked, otherwise treat this as the normal published extension
+      client.testing = false; 
       console.log("testing: " + client.testing);
 
       client.awc = new AWClient("aw-client-web", {testing: client.testing});
@@ -55,7 +56,8 @@ var client = {
   },
 
   getBucketId: function () {
-    return "aw-watcher-web-" + client.browserName.toLowerCase();
+    // Adjust to suit your needs…
+    return "aw-watcher-web-canary-" + client.browserName.toLowerCase();
   },
 
   updateSyncStatus: function(){

The specific key there allows this extension to be loaded as unpacked (in developer mode), BUT still use the 'production' chrome extension ID nglaklhklhcoonedhgnpgddginnjdadi. That's necessary now due to this check.

(Disclaimer: i don't really know what testing mode is really for, so perhaps using that is easier. But I just wanted to minimally fix this without worrying about the server running on a different port, etc.. )