Jeremy, TonyM, Another interesting sync adaptor would be one that *retrieved *and stored > tiddlers via the Wordpress API.
I think the main problem with "database backends" (Google Sheets, Wordpress, PouchDB) is that by default they are not accessible as a web page, but everyone has to set up credentials to read and edit the wiki. Sorry if I misunderstood it but haven't used Tiddly in this way. If I understand it, something like a database backend would look like this: * You open an empty Tiddly * Configure credentials for the saver * Saver synchronizes (downloads) tiddlers * When you make changes, the changes are saved to the database If it doesn't work that way, I apologize and please someone write down the workflow. The problem is you don't always want to give credentials - for example, you want to make tw.com visible without logging in. The easiest way to make your wiki public is to recreate the HTML (which anyone can read) after each change, and if you have credentials, you can also edit the tiddlers via this generated HTML. I find GitHub / GitLab best suited for this workflow, thanks to continous deployment. I would love to enable contributions to tiddler content via got hub a bit > like when you edit tiddlywiki.com but have the changes appear online. A workaround is to add new Personal Access Tokens to the repository, one for each user, so they will have their own "TiddlyWiki password". -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3f3dd877-878f-4ad3-9c4c-4b8bc752567c%40googlegroups.com.
