Jeremy et al..
I was going to raise this idea separately, but since it is somewhat related
I am adding here, I hope it is not "off topic", I don't think it is.
A TWX version as they say
In part reacting to your comments, an my morning coffees, here is my
related idea that this externalise approach may facilitate, the idea of
"compiling" a TiddlyWiki, perhaps compiling is not the correct word.
- Such that if such an externalised scripts method, could include some
user customised system tiddlers, it may be possible to place settings and
encryption keys into the tiddlers and external file,
such that it is effectively unreadable until it loads in the specific
wikis context (or group of wikis). Perhaps there is a public private key
pair between the shell wiki and the external scripts file. "You need one to
get the other, to get the first"
- A key could also be pulled from a user ID password file, so unless
logged in, they can not use the wiki.
- if the wiki is secured with a key in the user ID password File, they
would be prohibited from downloading a single file version they could read
without being given the key.
- This would allow secure documents and propriety information to be
published without concern of bulk theft.
- It may also allow people to sell end user licences copies of
tiddlywiki editions/solutions that are activated by saving a key, but which
once accessed largely remain an open source solution that can be changed.
- Editions or plugins could be distributed that generate the encrypted
script file and the shell wiki, or a wiki from the current file/folder wiki
which can then be placed online or network shares (in the multi-file form).
- An (encrypted) security feature could determine whether save as
(effectively generate a single file) is possible or not from a milti-file
- With node online every wiki can share this single external file, which
can be cached once for any network of wikis. This may get around the core
versioning issues and single file issues by making the split into multiple
files the last thing you do.
- This may also help reduce the save size of an online single file wiki
as implied elsewhere in this thread?, without resorting to a server.
I understand your desire to keep the single file model primary to
tiddlywiki, but as you can see with all the server solutions people are
trying to build more advanced versions to meet various requirements, If
such wikis can be exported as single file versions, whilst allowing them to
be secured sometimes, it is even more powerful.
In the future
- There may be a way to split out key macros to another encrypted file
so that some key algorithms can be exported, shared amongst wikis and not
visible in the main wiki file (An example could be a payment processing
module), Yes these things will be visible in memory but you are 99% of the
way of securing a TiddlyWiki from users, if they do not have a way to edit
key tiddlers and 90% of the way from securing it against hacking
(un-trusted users at least)
- For really large wikis online perhaps additional division of
externalised core or user static data could be done to further optimise
performance, like lazy load a products database.
The more secure TiddlyWiki is against hacking the easier it is to open
update access on the internet, for a higher level of interaction.
To me this ability for tiddlywiki to operate securely and at high
performance on the Internet is possibly the last border for tiddlywiki to
cross, to become truly a universal solution, I have at least three startup
ideas that could leverage this.
Post by Jeremy Ruston
tiddlywiki.js editions/tw5.com --build external-js
And then in the `editions/tw5.com/output` <http://tw5.com/output> folder
index.html - 3,889,031bytes
tiddlywiki.js - 1,878,319 bytes
For me the interesting one is empty.html which is 85 kByte with the new
That's very interesting for WebDav, if the js-part can be cached. ... BUT
it seems to mess up the existing file-saving extensions. ...
I need to make more tests, but I wouldn't recomment to use it for
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 firstname.lastname@example.org.
To post to this group, send email to ***@googlegroups.com.
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/61e05ab7-3f6f-4c51-b3a3-aab8f545808d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.