I am really impressed with this solution @valpackett, I had done a lot of research on this in the past, tried to encourage a PWA version to get past the saving issues with tiddlywiki, no click and use. But my skills were not broad enough in this area. Thank you.
But my own attempts to follow the instructions get lost due to jargon or need to know information (I dont have) to set up the server.
Please tell me If I am wrong;
The architecture of a PWA is that it is hosted at a location online, once you visit that website you can elect to install a local copy on your machine. It works and saves locally out of the box.
- Many PWA’s also allow the local copy to be synchronised online so that the same data become available if you run the same PWA on different devices or over time.
It seems to me we could make use of two PWA types
- PWA with server sync as described above, I will call this a “Roaming PWA”.
- A simpler version that can be obtained from a URL and installed locally and only used locally. Perhaps a “Local only PWA”
2.1 This is somewhat in keeping with owning your own data that a local tiddlywiki does so well, also if you have a node server you control.
The blockage for me is understanding how to implement the first “Roaming PWA” and understand how we could handle a lot of people subscribing to out PWA and the server implications.
I would also be keen to see if we can publish a tiddlywiki at a simple URL that people could then make it their own through a local PWA and solve their saving issues. This may not need additional internet resources or demand and ongoing “subscription”.
This is so important to me, and the ongoing success of tiddlywiki, I will offer any help needed to build documentation or custom solutions for making use of this technology. But of course until I can do it myself this will be difficult.
- A final issue to consider is users having PWA in which you can drop files and media to make use of the file uploads plugin approach, to save files externally (but local) and provide an external reference to them.
- For example to use ones local SSD/HDD/LAN to store the media and keep the wiki light. This local data storage can be much cheaper than online storage.
- This is not compatible with a roaming PWA, but does not depend on a server.
These solutions have the potential to go down in TiddlyWiki History as the day it became really available to everyone.
(shhh don’t tell Patreon staff but this is basically a trick to allow (something morally equivalent to) one-time donations, without the whole subscribe-and-unsubscribe dance)
