Well, difficult to say, although I now have some experience with Go, maintaining Timimi requires also some fundamental discussions, i.e. standandazing the event-based saving so that it can be implemented in TWC, and is extendable (for handling various cases of the saving itself, and also saving other files, including images, plus security topics). I’ve tried to start such a discussion, but didn’t get much attention/help. Currently, my preferred savers are MainTiddlySaver and the ContinuousSavingPlugin as a fallback (uses window.showOpenFilePicker and window.showSaveFilePicker, those looking for a way to save in Chrome may be interested in implementing a similar saver for TW5), and MTS is solid, i.e. won’t be hurt by further security restrictions (again, if we had a standart of IO interfaces, I could extend it to support TW5 as well). If I maintained Timimi, I’d probably rewrite it with Node.js, to allow more community members to collaborate on it. These days I’m focused on launching my own product, and it would be much more convenient for me to consult and help rather than be the maintainer of the Timimi successor.
One of the selling points on the Timini home page is how much faster it is because its written in Go. I have no experience, and little interest in the language. I do wonder how much of the extra speed is noticeable to end users, but I’m not a user of these tools, so I have little to offer.
OK. I only asked as yours was a name I recognized among the Timini contributors. I didn’t dig in to see whether that was one PR fixing a typo or months of active collaboration on major features.
Good luck on launching your product!
I realized a while back that Timimi is a surprisingly complex piece of software to support and maintain, and that unless more maintainers joined the effort, it’s just a matter of time before it’s not usable anymore.
(I think we can say that it has been abandoned, since the last commit was June 2022, despite some apparent and not too hard to solve problems for Snap and Apple Silicon.)
As I understand it, Timimi consists of:
- A (built-in) TiddlyWiki saver plugin
- A Chrome extension
- A Firefox extension
- A binary, cross-platform host application that should work on and be compiled to Windows, MacOS and Linux
- A Linux installer
- A Windows installer for Chrome
- A Windows installer for Firefox (registers timimi.exe in the Registry in a different place)
The extensions must be updated when browsers require changes, and the installers and binaries when the different OSes etc change their requirements and assumptions.
Currently, the Manifest debacle should probably be prioritized, then a new Snap-compatible installer and an installer for Mac OS (maybe just Apple Silicon, I don’t know).
Are you as a community up for the challenge? 
I’m not sure about the protocol here.
@FSpark Is it ok with you if I produce a side-loadable extension here based on your manifest-3 work ?
Backgrounder: Extensions can be side-loaded in Chrome’s developer mode (you just slide a switch to turn on the mode). This is how @buggyj distributes TiddlyClip, for instance. In the case of Timimi, there are additional tweaks to your system that have to be made.
For an extension to be available on the Chrome extension store, someone will have to register as a Chrome developer. Last time I checked this was $25 – a real bargain compared to apple, BTW. But extensions can also be side-loaded locally, though the intention was testing for development.
re: timimi on apple silicon, you’ve probably already tried Timimi extension not getting access to local TiddlyWiki (macOS Sonoma; Apple Silicon; Chrome 120.0.6099.129) · Issue #94 · ibnishak/Timimi · GitHub
is there something else that is not working on apple silicon?
Of course, I mentioned it before in this post.
Thank you very much!
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.
The extension itself:
The Linux installer
Wow, you too? I thought I was the only one!
Are one and only coterminus in Math?
Just asking, TT
Just in case I buried the lede, the extension here is for all Chrome users – not just Linux users – if they’re willing to make a small edit to a text file. Of course, you don’t have to actually do anything until June.
I won’t. Too many other things are afoot.
A comment from the worrying-side.
TT
It’s a lot easier to paint the house when it’s not on fire.
But maybe people have already stopped using Timimi?
I guess.
FWIW I am still using Timimi 1 (not what most use) on FF that gives a back-end to invoke programs, still.
My point? Everything got fragmented. A war on making sense.
A big concern for TW is local saving.
I hope that someone like you could make a back-end to help save saving.
TT, j x
I am using Timini and would like to continue doing so…
I hope you can all appreciate why getting information “saved” easily would be important to a Christian missionary like me! 
I wouldn’t know. I’ve had so many note systems, most of my data is in limbo.
Per the notes above, you should be able to use a local Timimi extension, coupled with a small edit to a simple json file, to continue using Timimi now. Even though you could wait until June, if you do it now then we will have feedback regarding @FSpark 's extension fix.
So far there have been only two downloads of add-on-chrome.zip . Which is why I’m wondering if there is much interest.
I am confused by your comment. I am, in fact, using Timimi on Google Chrome now, with no special json file.
A Chrome popup told me that Timimi was untrusted, and made me click a button in the popup to continue using it, but with the warning that I was taking my life and the future of the Western world into my hands.
Even my original post stated “I was able to force it on again.” My concern is not about my current activity, which is unhindered, but to activity when Google finally decides to block Timimi. You and others are mentioning something about June? So I am assuming you have read something I have not personally seen.
As I stated in a reply above, I will continue to use Timimi until it stops working. When it does, I will evaluate the options I have at this point. So far, TiddlyStow (version 1) seemed the easiest. But there are other options here, or mentioned in other threads, such as TiddlyStow v2.
But thinking about people other than myself, who are coming to TiddlyWiki for the first time, there is a definite value for having a Google-approved app like Timimi for saving changes, with easy and clear instructions on how to set it up, as opposed to making them go into Command Prompt or GitHub, or download something linked to from here, any of which could scare them off because they might see it as complicated and confusing / unapproved / unsafe.
So I would still hope that by the time the day comes when Timimi as it stands will no longer work, that there will exist an updated Timimi or equivalent in the Chrome store.
You are using a json file! It got installed when you ran the Timimi installer.
Yes, the word on the street is that June is when full enforcement begins. However, Google has moved dates around before, so who knows?
We’re all concerned that June date. Which is why there is a solution provided above.
If you scroll up to my prior post you will see that I have provided a zip file. It is possible to unzip this and then load it into Chrome locally (after removing the existing Timimi extension). This extension is compliant with Chrome’s new rules. BUT, it doesn’t work until you also edit a file. For windows, the path should be:
C:\Users\<your account>\AppData\Roaming\Timimi-Chrome\timimi.json
There’s an id that needs to be written over in order to allow the new extension to work (per the post above). Hopefully that explains it a bit betterr.
Hi @Mark_S
As a macOS user (Sequoia, 15.3.2), I’m writing to say thanks a lot: I followed your instructions step by step, and your update to the saver works great. I didn’t delete Timimi from Chrome, just kept it “off” (default setting with new Chrome) and then followed your guide to download, install, and edit the manifest.json file. Chrome now shows Timimi as installed and running normally (no message about incompatibility anymore), and even the lovely fish icon is the same.
I normally use Firefox with Timimi to save my single-file TWs, but your update is great to have, and could mean a switch to Chrome if Firefox goes down the Manifest 3 path.
Simon
PS I now have goldfish name envy, which I didn’t even realise might be a thing (mine was called Number 6, after the character in the Prisoner, though now that just seems ordinary …)
PPS / edit: Oh, and on saving the TW file, I get a copy in the backup folder I set, using the “Tower of Hanoi” method set by clicking the Timimi fish icon – all as expected. Thanks again: brilliant!