Hi Xavier

> I'm quite new @ TiddlyWiki and I need some guidance.

Welcome to the project!

> I try to develop a new plugin to store tiddlers on IPFS.
> I hardly studied a few SyncAdaptor implementation but I'm lost :
> - https://github.com/wshallum/couchadaptor
> - https://github.com/linonetwo/solid-tiddlywiki-syncadaptor
> - https://github.com/fiatjaf/tiddlywiki-remotestorage
> - https://github.com/bourgeoa/tiddlywiki-node-solid-server
> Here is what I want to achieve :
> - load a plain tiddlywiki (I'm planning to offer my users a set of predefined 
> wikis, probably on IPFS but self-contained)

The general approach taken by the sync mechanism has two parts:

* A means to construct a TW5 HTML file from the constituent tiddler files
* A mechanism to sync individual tiddler changes from that HTML file back to 
the server

It is orthogonal to the saver mechanism which is concerned with saving the 
entire HTML file as a single file.

The two mechanisms are pretty much independent: one can be syncing individual 
tiddlers to a server and then simultaneously use the saver mechanism to save a 
snapshot of the entire wiki.

One crucial difference is that the syncer mechanism requires an external 
process to build the HTML file. That is done dynamically in the default client 
server configuration: the route `/` triggers a build of the entire wiki. It can 
also be done by an external build process that periodically rebuilds the HTML 
file.

> - the plugin is loaded but should be inert until the first save to the 
> appropriate server. The first save should analyse the content and upload the 
> content to IPFS.
> Each tiddlers in a separate file, especially for external attached file. 
> Maybe the first step is to have a self contained file ??

IPFS is static storage so yes, I think it would be much easier to focus on the 
single file configuration.

> Question :
> - how do I detect that the wiki is not fully IPFSified yet ? probably a 
> property, but where ?)

I'm not sure what you mean here?

> - how to I bypass the SyncAdaptor (inert) during the first load ?

When it starts up, the sync adaptor should interrogate the server to obtain any 
tiddlers that have been updated since the HTML file was built.

> - It is not clear yet how savers and syncadaptors are processed :
> Let's say that you setup a github account and you have also the IPFS 
> syncadaptor.
> Who's winning, the saver or the SyncAdaptor.
> A lot of questions I agree. I hope that my questions make sense and are clear.
> Thanks

No problem, I hope my brief answers help, please don't hesitate to ask 
followups. These kinds of discussions can be helpful for observers, too.

Best wishes

Jeremy

> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" 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/tiddlywikidev/004560cd-7acf-4408-a3b2-63e049db291a%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev/4FC3FC4C-EB5D-444A-A439-1ABE76EEF3EF%40gmail.com.

Reply via email to