The Original thread is just one answer to the more general issue of multi-device use of a tiddlywiki.
Ideally you would have one source of truth, such as an online wiki and take steps with Local storage to allow off line use. For the occasions where one or more devices are offline and you could make un-synced changes, a method to set which device is the owner of the wiki can also be developed to protect the integrity of the files.
Ideally the single source of truth would be a Bob multi-user implementation and at the most the conflict would be only at a tiddler level if at all. I believe you can still use local storage for offline use in Bob as well (not recently verified).
However
There is often other opportunities when you step back and think about the real world problem for example;
- if your aim is to have a “portable tiddlywiki”, one you use on your desktop but is available when mobile, and as a result you always have your mobile with you (but not your desktop) then it may be as simple as keeping the wiki on your mobile, but allowing you to access it when on the network from your desktop. When using it on the desktop you could do a desktop backup in case you loose your mobile. That is the mobile becomes the source of truth
- Using a mobile to desktop sync method may work but it adds a level of complexity and risk you may be able to avoid. Just access it from the desktop directly on the phone via the file system when USB connected or wirelessly.
- Adding a little switch so the Mobile can have “it open for edit”, then release it for edit on the desktop and visa versa would help. I have done some proof of concept designs on this.
Alternatively although somewhat convoluted you could install Bob on your mobile (android at least) via Termux and allow multiple access via wifi from your desktop, so the mobile is the source of truth and also a multi-access multi-user server that your desktop can access (only on the LAN).
It is always worth stepping back and looking at the big picture and usage patterns before focusing on a specific technical solution. However as a professional in IT I have found its almost impossible to teach people how to do this, even document it, because there are always many variables and especially the multi-variable humans that are involved.
That reminds me of the Joke;
The most unpredictable part of a vehicle is the “Nut behind the wheel”