Josiah is making a subtle, and useful, point in relation to some of the remarks I’ve made in the past.
Those remarks were about the way that TiddlyWiki has a central duality: it exists both in its standalone HTML file form, and as a much more traditional Node.js server application. Both aspects of TiddlyWiki are important; in particular, the Node.js configuration is used to build the standalone configuration in the first place. The concerns that I have expressed are about the tension between developing and promoting the standalone features that make TiddlyWiki unique versus the server-based features that (could) make TiddlyWiki much more familiar to a general audience. I interpreted Josiah’s remarks as being a vote of support for continuing to emphasise the standalone configuration, and thus the unique use cases that can only be tackled by TiddlyWiki. He’s echoing a thought we’ve discussed before: that most of the users of TiddlyWiki are invisible, because it is used privately, and so posting here makes good sense. Josiah’s suggesting of making it easier to post to social networks is one of the core ideas explored by the IndieWebCamp community: https://indiewebcamp.com I’d agree that such functionality would be useful in TW. I frequently draft GitHub issues in TiddlyWiki (as a Markdown tiddler) and then manually copy and paste it into GitHub. Direct posting via the API would be pretty useful sometimes. In closing, my personal opinion remains that it is the standalone configuration that makes TiddlyWiki special, and that the Node.js configuration exists to serve that configuration. I do want to improve the multi-user experience, but even there I want to retain the value of the standalone configuration, by making it easy to work on updates offline and collaboratively merge them later. Best wishes Jeremy > On 26 Apr 2016, at 13:30, [email protected] wrote: > > Ciao Jeremy > > Both here and on the Dev channel I have seen you write about your concerns, > in last few days, about taking TW too far towards server dependent systems. > > I TOTALLY AGREE. > > I am one of the silent users of TW. I developed, for my own use, many > customized versions. I never publish them. I just use them locally. > > The idea TW step more towards on-line server mediated systems would erase its > specialness, IMO. > > The one area where TW might be improved, for me, is being able to POST to > social networks more easily. BUT interactive stuff that REQUIRES DEPENDENT > linkage to function is not a good idea to have at the front. > > Its not that I, in anyway, think that "scaling up for server services" is bad > per se. However, the MINIMALIST MODEL of the ONE-PAGE is, undoubtedly, its > brilliance. > > Many thanks for inventing this thing, > Josiah > > > -- > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywiki > <https://groups.google.com/group/tiddlywiki>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/f6b3756c-6a72-410f-bd1a-2376ed927860%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/f6b3756c-6a72-410f-bd1a-2376ed927860%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/52C313A5-3C14-4DE1-9D0E-8BD3B384752E%40gmail.com. For more options, visit https://groups.google.com/d/optout.
