So I think I worked out how to compile and set up the extension and saver for Chrome on Linux (not Snap). Are there any brave Linux users that want to try it?
In any event, you should be able to use this extension on Linux/Windows/Mac after some tweaking. This extension fix is actually from @FSpark – I’m just putting the pieces together here.
You unzip the addon-chrome.zip
file to some safe directory (pick a place you won’t delete). You go into your extensions manager on Chrome and turn on developer mode. Then “Load Unpacked Extension”. Navigate to the directory with the manifest.json
file and load. The Timimi extension should appear. It’s 99% the same as the original, and will navigate to the old write-up.
Note that this extension should work for Chrome on Linux, Windows, and Mac. I’ve tested it on Linux and a very, very old Windows. A report on Mac would be helpful.
But this isn’t enough. The problem is that there is a configuration file that needs to be updated with the id of the extension. In the following, it’s assumed that you have installed Timimi as a regular user, and not as a corporate user. Verify that your newly loaded extension has an id of “eckkbhekakplhjeabeoechennfbclgng” . This happened to be the name of my first goldfish, so it was easy to remember.
For Linux, the path to the configuration is:
~/.config/google-chrome/NativeMessagingHosts/timimi.json
For Windows, the path should be:
C:\Users\<your account>\AppData\Roaming\Timimi-Chrome\timimi.json
(it could be a different drive depending on your configuration.)
For Mac the path should be:
$HOME/Library/Application Support/Google/Chrome/NativeMessagingHosts/timimi.json
In timimi.json
there is a line to be edited for “allowed_origins”. The line for allowed origins in the timimi.json file should look like this after editing:
"allowed_origins": ["chrome-extension://eckkbhekakplhjeabeoechennfbclgng/"]
For Linux, I’ve compiled an installer which will do this reconfiguration for you. To use it, download the timimi-test.sh file, set to executable and run (this is the brave part). In the menu, select Chrome for your installation. Hopefully it will run ok. This installs the “timimi” file (which hasn’t actually changed) over-writes a timimi-json file with the new id of the “new” extension. Be aware that installing this might zap your old Timimi settings, so if you are still using it under the grace periood of manifest 2, … be aware.
But I guess it would be useful to know if my newly fledged “go” compilation skills work for anyone else. If there were any tweaks to the code after it was submitted to github … then the code here will be wrong.