Points taken, I guess a lot of it comes down to how TW is being used. I would maintain that when a TW is passed on it is either intended as a fork (clone) or a read only source. Collaboration is basically out.
A situation in which a users works with localStorage 99% of the time and then exports to html is conceivably a good compromise. The fact remains that localStorage is the HTML5 way to do hassle free local saving. Exporting to publish and share is a different use case and the target could be files or the cloud. The issue with security is still one I would contest as it remains no worse than the situation today: if you download a TW and it is allowed to save then it could also clobber or read your existing TWs. Someone who wants a high level of security could encrypt. -- 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 http://groups.google.com/group/tiddlywiki?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
