Post Script, Allowing people to annotate or comment on tiddlers, perhaps part of this need to share tiddlers could also be achieved with NoteSelf using the local pouchDB to save changes, the user can then export their annotations and send an email, post etc... a json file to the site owner who can import them, it would take very little to design an alternate import process that allowed a difference review of each inbound tiddler, and an acceptance, rejection or hold response to each tiddler. And while this seems a manual process the fact is the user may not want it any other way because they wish to accept or reject the submitted tiddlers.
Regards Tony On Monday, June 11, 2018 at 10:59:00 AM UTC+10, TonyM wrote: > > I would like to add something here and I hope I may be able to state it > clearly. > > - We can already effectively store and share tiddlers and groups of > tiddlers, we can drag and drop, import and export. > - It seems to me this thread is considering the "Ultimate" integrated > transfer or subscription process" when 98% of what is required already > exists. > - I am all for the ultimate solution but this is to me putting the > cart before the horse, > - In building my own tiddlyWiki network, to share and distribute > plugins and other wikis I have used existing tools to do this > > It seems to me that a large part of this solution can occur at the wiki > implementation level, without plugins or core changes. > > Of course my implementation has limits but actually there are a few > features that would allow it to become a full solution. Here is a non > exhaustive list of the top of my head. > > - At TiddlyWiki load time checking for the existence of a named file > such as a Json file and importing it, > - Use file time stamps to avoid doing it more than once until it > changes. > - Provide a logout or exit process, or within the save process to > export a json file with selected tiddler once a tiddler changes. > - Mark tiddlers as owned by a specific wiki, and allow edit in that > wiki and avoid edit in other wikis. > - This entails a method to register wikis > - Using iframe embedding external wikis, works well to open a window > and permit drag drop of tiddler such as plugtins between TiddlyWikis > - This however requires selecting import in the destination wiki > - Or still seeing the side bar etc.. when displaying a foreign > tiddler > - Providing a way to open a Wiki with the focus on a single tiddler > would help here. > > Each of these features should be fairly easy to implement > If we then combined the above with a set of practices or plugin support > people could then build loosely coupled networks of wikis with shared > tiddlers. > > In conclusion, a lot could be done in the implementation space with > support from a few tools. This can then be extended with features in > platforms such as Node, Bob to build highly scale-able tiddler distribution > hubs. > > Regards > Tony > > > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/8f93f391-7b77-45ac-a112-4a71e35933eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
