Okay, I suppose I'll see if the text outgrows the single '.html' file approach with the splash screen, while keeping media relatively linked.
I would like to know a bit about TiddlyWiki versus NoteSelf. Comparing them: - *How do I host without the public being able to change what is being hosted on the server?* I don't mind if they can change their local version. - *What is the workflow for making changes to the hosted file?* For example, is this done directly as in NoteSelf's CouchDB sync, or is a local copy changed and uploaded using SSH? - *Are there any other differences I should know about?* On Sunday, January 6, 2019 at 4:13:42 AM UTC, TonyM wrote: > > Kalcifer, > > The best solution varies due to a number of factors. You can have a lot of > text and interactions in a tiddlywiki without it being too big. Using the > loading splash screen can stop people abandoning your site before it fully > loads then it is in the browser cache and memory and performs well, even > better than other sites. > > The main reason tiddlywikis get ovesized is media, such as images and > these can be externalised and loaded on demand. > > Using noteself, rather than read only, keeps your hosted copy readonly but > allows the visitor to save changes in their browser session. > > Perhaps share some more details so we can give taylored advice. > > Tony > > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/3968cc3a-a671-4123-b72f-93370175b47e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
