My first thought is, there goes the privacy of using TiddlyWiki. Google isn't free. You pay by giving up your privacy. Granted, I don't have anything on a publicly accessible tiddlywiki site that is all that private but I do use it at home and it is nobody's business but mine what I keep there or when I access it.
Which CDN do you propose to host it? What happens when it gets hacked and all of us suddenly have exploit code inside our tiddlywikis? What happens if the country that the CDN is in decides to order them to include spyware? What happens if the country it is in outlaws consumer encryption, are we going to lose the 'encrypt tiddler' option? Are we still going to see the button but not know about the backdoor that got forced to be put in? If that doesn't sell you, and plenty of people have given up on having any personal privacy or real security so I accept it may not. My tiddlywiki at home works even when the Internet connection goes down. Even if I have a completely empty cache. It works on my laptop locally when there is no wifi. Tiddlywiki just works and that is a big selling point for me. Finally, gzip an empty.html tiddlywiki. How big is it now? Because that is the size that actually matters. Modern web browsers and web servers (all the big ones like iis, apache, nginx, and even lighttpd) all support compressing static content before delivery. So, what actually goes across the wire on a properly configured web server is considerably less that the uncompressed file size if the web server was configured to support it. On Tuesday, May 9, 2017 at 11:23:21 AM UTC-4, Arlen Beiler wrote: > > Yes, yes, I know. TiddlyWiki is supposed to be a single file architecture. > And it is. And it will be when I am done with this too. So hear me out. > > As I am working on an upgrade to the current TiddlyWiki Cloud Dropbox > saver. I keep thinking that there has to be a better way than uploading 1.5 > MB every time. I know full well what most of that space is. Its mostly one > very crucial and important plugin that never changes without an official > release of TiddlyWiki. Because it IS TiddlyWiki. I am of course referring > to $:/core. > > It weighs a whopping 1.2 MB. Not much compared to some libraries, but it > is a bit. And I wonder if there isn't some way that we can put that file > somewhere online so that as we get into Federation and more online hosting > and collaboration using TiddlyWiki, we don't have to keep GBs of TiddlyWiki > Core 5.1.14 (and then 15, and so on) in our cache and constantly > redownloading it everytime we visit a new website. > > That's the main point. TiddlyWikis that are hosted online don't need to > contain their own copy of the core. They should be able to use the copy > that get's downloaded from the CDN, since then you can cache that copy and > use it on every website you visit. > > We could add a second button in the Control Panel that would allow you to > download a TiddlyWiki with a reference to the correct version on the CDN > instead of the including the core in the download. There should also be an > easy way for the renderer to know whether it is supposed to add the core or > include the link. > > I think the link should be in head and I don't know for sure but I am > imagining that it would use the preloadTiddlers mechanism. Or it should be > included directly before bootprefix or which ever script tag brings in the > preloadedTiddlers. > > Anyway, thoughts? > > -Arlen > -- 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/509a6e22-7f1e-40c1-b592-d62e5d6fe95c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
