Docs updates

Including a new tiddler about the Firefox Apocalypse

editions/tw5.com/tiddlers/community/resources/Full Text Search Plugin by Rob Hoelz.tid

@@ -0,0 +1,16 @@
+created: 20171109171703588
+modified: 20171109171922913
+tags: Resources plugins
+title: Full Text Search Plugin by Rob Hoelz
+type: text/vnd.tiddlywiki
+url: https://hoelz.ro/files/fts.html
+
+A plugin to integrate the popular [[lunr.js|https://lunrjs.com/]] search engine, giving TiddlyWiki much more sophisticated search capabilities:
+
+{{!!url}}
+
+<<<
+Provides an alternative search result list that orders results by search relevance and ignores differences in word forms (ex. //tag// vs //tags//).
+
+On my personal wiki, I have the problem that there are terms I use across a lot of tiddlers, and sometimes I'll use different forms (such as the aforementioned //tag// vs //tags//).  I wanted a plugin to allow me to find the tiddler I'm looking for quickly and didn't require me to worry about how I declined a noun or inflected a verb - so I wrote this plugin, which provides an alternative search list powered by [[lunr.js|https://lunrjs.com/]].
+<<<

editions/tw5.com/tiddlers/community/resources/TiddlyDrive Add-on for Google Drive by Joshua Stubbs.tid

@@ -0,0 +1,16 @@
+created: 20171109172705241
+modified: 20171109172934929
+tags: Resources plugins
+title: TiddlyDrive Add-on for Google Drive by Joshua Stubbs
+type: text/vnd.tiddlywiki
+url: https://chrome.google.com/webstore/detail/tiddly-drive/oaphhjhbbabdjnpjpiliepphpmnioolo
+
+An add-on for Google Drive that allows TiddlyWiki files stored there to be opened and saved directly
+
+{{!!url}}
+
+<<<
+I made an app that lets one edit TiddlyWiki files saved in your Google drive and then saving them back automagically. The page is here https://chrome.google.com/webstore/detail/tiddly-drive/oaphhjhbbabdjnpjpiliepphpmnioolo but I think you need to add it from the Google Drive web interface.
+
+I even added an optional ability to save with ctrl + s hotkeys.
+<<< [[Joshua's launch post|https://groups.google.com/d/topic/tiddlywiki/7pNJizR57e8/discussion]]

editions/tw5.com/tiddlers/community/resources/TiddlyServer by Arlen Beiler.tid

@@ -0,0 +1,22 @@
+created: 20171109171415540
+modified: 20171109171644007
+tags: Resources
+title: TiddlyServer by Arlen Beiler
+type: text/vnd.tiddlywiki
+url: https://github.com/Arlen22/TiddlyServer
+
+An extension to the Node.js configuration of TiddlyWiki that adds support for static attachments and for working with multiple wikis at the same time.
+
+{{!!url}}
+
+<<<
+TiddlyServer 2.0 takes the server command of TiddlyWiki on NodeJS and adds it to a static file server. This means you can load and serve any TiddlyWiki data folder in the same way you can serve a single file TiddlyWiki.
+
+But you don't need to serve files and folders from just one place, you can serve them from multiple places anywhere on your harddrive (literally anywhere NodeJS can stat, readdir, and readFile). You can even organize them into virtual folders (aka aliases in Apache and mounts in Express).
+
+The main point, of course, is that you can actually edit your files, not just look at them. Single file TiddlyWikis use the put saver, which needs to be patched using a bookmarklet included on the index page. The instructions for this are below under the heading "One thing that needs to be noted".
+
+And, of course, you can edit data folder tiddlywikis just like you were running node tiddlywiki.js data --server, except that you run it on the path that you found it at (e.g. http://localhost/personal/notes/). You can have as many data folders open as you want, they don't conflict (though they will each take memory).
+
+Data folders store individual tiddlers instead of entire wikis. They take less disk space as they also do not store the core and plugins. This means they also save much quicker, especially over the internet. They also save immediately (within 10 seconds or so) and they save drafts.
+<<<

editions/tw5.com/tiddlers/community/resources/_savetiddlers_ Extension for Chrome and Firefox by buggyj.tid

@@ -0,0 +1,10 @@
+created: 20171109171935039
+modified: 20171109172424843
+tags: Resources plugins
+title: "savetiddlers" Extension for Chrome and Firefox by buggyj
+type: text/vnd.tiddlywiki
+url: https://github.com/buggyj/savetiddlers
+
+An extension for Google Chrome and Mozilla Firefox that smoothes out some of the friction from TiddlyWiki's built-in [[HTML5 fallback saver|Saving with the HTML5 fallback saver]], making it almost as easy to use as TiddlyFox once it is set up correctly.
+
+{{!!url}}

editions/tw5.com/tiddlers/definitions/Quine.tid

@@ -1,6 +1,11 @@
-title: Quine
+created: 20171110100048967
+modified: 20171110100146695
 tags: Definitions
+title: Quine
+type: text/vnd.tiddlywiki
 
 Wikipedia [[defines a Quine|http://en.wikipedia.org/wiki/Quine_(computing)]] as //a computer program which takes no input and produces a copy of its own source code as its only output//.
 
 TiddlyWiki is an unusual example of a practical quine: it is this ability to produce a copy of its own source code that lies at the heart of TiddlyWiki's ability to independently save changes to itself.
+
+"Quine" is also the name of [[the unofficial TiddlyWiki application for iPhone/iPad|Saving on iPad/iPhone]]

editions/tw5.com/tiddlers/definitions/TiddlyFox.tid

@@ -1,10 +1,12 @@
 created: 20130825161100000
-modified: 20160601160149340
+modified: 20171110094548887
 tags: Definitions
 title: TiddlyFox
 type: text/vnd.tiddlywiki
 
-TiddlyFox is an extension for Firefox that allows standalone TiddlyWiki files to save their changes directly to the file system. TiddlyFox works on both desktop and smartphone versions of [[Firefox]]. See [[Saving with TiddlyFox]] or [[Saving with TiddlyFox on Android]] for detailed instructions.
+TiddlyFox is an extension for older versions of Firefox that allows standalone TiddlyWiki files to save their changes directly to the file system. TiddlyFox works on both desktop and smartphone versions of [[Firefox]]. See [[Saving with TiddlyFox]] or [[Saving with TiddlyFox on Android]] for detailed instructions.
+
+TiddlyFox is now obsolete due to its incompatibility with the latest versions of Firefox - see [[Firefox Apocalypse]]. There are many alternatives to TiddlyFox, but none that work in precisely the same way -- see GettingStarted for details.
 
 TiddlyFox can be downloaded from the Mozilla Addons site:
 

editions/tw5.com/tiddlers/hellothere/HelloThumbnail.tid

@@ -1,5 +1,5 @@
 created: 20150414070451144
-list: [[HelloThumbnail - Introduction Video]] [[HelloThumbnail - Gentle Guide]] [[HelloThumbnail - Latest Version]] [[HelloThumbnail - TiddlyMap]] [[HelloThumbnail - HelpingTiddlyWiki]] [[HelloThumbnail - Developers]] [[HelloThumbnail - Classic]]
+list: [[HelloThumbnail - Introduction Video]] [[HelloThumbnail - Gentle Guide]] [[HelloThumbnail - Firefox Apocalypse]] [[HelloThumbnail - Latest Version]] [[HelloThumbnail - TiddlyMap]] [[HelloThumbnail - HelpingTiddlyWiki]] [[HelloThumbnail - Developers]] [[HelloThumbnail - Classic]]
 modified: 20150414070948246
 title: HelloThumbnail
 type: text/vnd.tiddlywiki

editions/tw5.com/tiddlers/hellothere/thumbnails/HelloThumbnail - Firefox Apocalypse.tid

@@ -0,0 +1,7 @@
+title: HelloThumbnail - Firefox Apocalypse
+tags: HelloThumbnail
+color: #B7D5EA
+background-color: #fff
+caption: Firefox Apocalypse
+link: Firefox Apocalypse
+image: Firefox Apocalypse.png

editions/tw5.com/tiddlers/hellothere/thumbnails/HelloThumbnail - TWEUM2017.tid

@@ -1,5 +1,5 @@
 title: HelloThumbnail - TWEUM2017
-tags: HelloThumbnail
+tags: HelloThumbnail-disabled
 color: #fff
 background-color: #000
 icon: <span style="font-size:3.5em;font-weight:bold;text-shadow:1px 1px 3px rgba(0,0,0,1);">2017</span>

editions/tw5.com/tiddlers/images/Firefox Apocalypse.png.meta

@@ -0,0 +1,3 @@
+title: Firefox Apocalypse.png
+type: image/png
+tags: picture

editions/tw5.com/tiddlers/platforms/Firefox Apocalypse.tid

@@ -0,0 +1,45 @@
+created: 20171109170823847
+modified: 20171110100253897
+tags: Platforms
+title: Firefox Apocalypse
+type: text/vnd.tiddlywiki
+
+! Summary
+
+On 14th November 2017 Mozilla will [[release Firefox 57|https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-beta-developer-edition/]], a major new version with many improvements and security enhancements. However, in amongst those improvements are ''some fundamental changes to Firefox's security model with the unfortunate effect of making it impossible for ~TiddlyFox to function''.
+
+TiddlyFox will remain available for people who [[continue to use older versions of Firefox|https://groups.google.com/d/topic/tiddlywiki/OJQ0yRq4zog/discussion]], but anyone upgrading to the new version will need to choose a new way to handle saving changes with TiddlyWiki.
+
+Happily, several new ways of working with TiddlyWiki now exist so that users have many alternative choices -- see GettingStarted for details. The demise of TiddlyFox has provoked several of these recent developments and thus may well ultimately be good for the community.
+
+There is a [[discussion thread|https://groups.google.com/d/topic/tiddlywiki/LcldXzPlTK0/discussion]] on the TiddlyWiki forums about these developments.
+
+! Background
+
+Firefox was first released in November 2004, a few months after the first version of TiddlyWiki. It was in many ways the Millenium Falcon to Microsoft's Death Star (in the shape of Internet Explorer). IE had by then enjoyed more than 5 years as the dominant browser, leading many in the web community to be frustrated that Microsoft's self-serving extensions to HTML had become de facto standards at the expense of innovation that might benefit the web community as a whole.
+
+Firefox quickly became successful because it managed to render web pages with close enough compatibly with Internet Exploer while offering a superior user experience. A large part of the promise of that user experience was the ability for any user to customise every aspect of the browser. Two innovations were behind this:
+
+* The entire user interface of the browser was constructed in [[XUL|https://en.wikipedia.org/wiki/XUL]], effectively an extension of HTML that enabled it to render conventional user interfaces (at the time, HTML was largely restricted to simple document-oriented layouts). Tweaking a few lines of XUL code could make wholesale changes to the user interface of the browser
+* The Mozilla add-on architecture gave full privileges to add-ons, enabling them to observe and interact deeply with the browser engine itself, and the file system of the computer on which it was running
+
+These two conditions enabled a vibrant ecosystem of Firefox add-ons, many of them extremely popular. In many cases, innovations that were first seen in browser add-ons later became integrated into the browser itself, most notably the web debugger [[Firebug|https://en.wikipedia.org/wiki/Firebug_(software)]] which was eventually cloned by all the browser manufacturers.
+
+Firefox continued to be extremely popular until Google joined the development of the rival ~WebKit browser to make Chrome. Google took a very different approach to the trade offs of making a browser, focusing on improving security at the expense of almost all other considerations. They pioneered approaches such as isolating each tab in its own process that were quickly adopted by all other major browsers.
+
+Google's approach precluded them adopting Mozilla's free-for-all approach to add-ons. Instead of having access to the entire browser environment and filing system, add-ons in Chrome see only a restricted subset of what is going on within the browser, and enjoy little or no access to the resources of the host machine.
+
+It was inevitable that Mozilla would eventually adopt Google's approach to [[browser security vis-a-vis add-ons|https://support.mozilla.org/en-US/kb/firefox-add-technology-modernizing]]. There is a point at which it wouldn't be responsible for Mozilla to be releasing a browser that had knowingly worse security than the market leader.
+
+! Lessons
+
+Some of the fecundity of the TiddlyWiki ecosystem stems from the adoption of the above two principles from Firefox:
+
+* Making the application user interface out of the same primitives as the application content
+* Giving add-ons free rein to observe and interact with all of the internal logic of the application
+
+Those two characteristics present similar security challenges to TiddlyWiki as they did to Firefox. A TiddlyWiki that was primarily focused on security would need to curtail those abilities.
+
+! The Future
+
+Innovation on new browser-based user interfaces and capabilities has now shifted from browser extensions to a new generation of frameworks that simplify creation of a custom browser based on an off-the-shelf open source HTML rendering engine. TiddlyDesktop uses [[nwjs|https://nwjs.io]], but [[Electron|https://electron.atom.io/]] is now very popular too.