I am really keen to see this working. I think the lack of response on 
muilti-user is not because there is no demand but because it has a number 
of pre-requisite knowledge to understand, and people have been struggling 
with it for some time.

I for one want it very much, only it needs to be lower on my to do list 
because of other priorities I have building TiddlyWiki solutions. Of course 
a multi-user tiddlywiki that is accessible on the Internet is also a big 

Some unstructured thoughts

I feel the default port should be a little more unique as there are an 
increasing number of solutions appearing on ports 80 and 8080 out of the 
box including many nodeJS solutions such as TiddlyDesktop and TiddlyServer. 
eg perhaps 8087

The single executable would be great however could there be some 
customisation read from a settings file distributed with it, so It can be 
reconfigured with various defaults and even a default TiddlyWiki (not 
Empty). I am interested in being able to distribute solutions not only a 
tiddlywiki platform. Perhaps the executable could look for index.html and 
load that at the root address?

I have looked into portable apps and it can be simple if what you package 
is simple. However it is immensely configurable..

If we distributed solutions packaged with an executable it is foreseeable 
two executables would be installed, I wonder how these could interact. Or 
should solutions always be deployed seperately with your executable 
considered a platform?
Could subsequent executable s use the "next Port"?

Good work

On Monday, March 12, 2018 at 5:00:26 AM UTC+11, Jed Carty wrote:
> The point of what I described is that you run an executable file and then 
> a working wiki opens in your browser and you don't have to think about it. 
> That is what I have set up and what I am asking about.

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 post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

Reply via email to