Consider doing what I did when Firefox broke some of the features on tiddlywiki classic, particularly "LessBackupsPlugin".
Firefox no longer allowed tiddlywiki to delete extra tiddlywiki backups. So, I installed a portable, old version of firefox, entered gobblydygook into the proxy settings so that this would basically be a semi-sandboxed firefox that couldn't even connect to the internet, and voila, it works as basically a standalone tiddlywiki app. But of course, that's all it does. If you're writing a novel, I might suggest Scrivener. Scrivener 3 is coming out in the next few weeks, and it's everything I could ever dream. It's more useful on Mac than on Windows, so you'll have to wait a bit longer for the functionality to catch up. The 30 day trial version only counts days that you actually use it, which is pretty awesome. On Sunday, November 12, 2017 at 3:57:39 PM UTC-7, Donald Bosart wrote: > > OK. I finally became desperate enough to post here. > > Background: > > I'm a longtime TiddlyWiki user who started out with Classic long ago > before it was "Classic" and have moved on to TW5 for some time now. I > won't bore everyone with all of the things I like about TW; but, it being > file based with a simple markup and having easy Tiddler creation and being > a "Guerrilla Wiki" that I could put on an Apache server to publish one-way > content for my group at work are among the best things since apple pie... > > Alas, file:// protocol seems dead; long live file protocol. It was great; > use it to author... put the file on a server and it is automatically > protected via http.... wonderful... FF with TiddlyFox to author, scp to the > server and use Chrome to view (most everyone at work uses Chrome). > > With the imminent arrival of FF 57 I've been following the various threads > here and trying to discern a way forward. My immediate action both on my > work machines and at home was to turn automatic updates of FF off before my > authoring tool becomes caput. But that's temporary... > > So what is the best course forward? Should I bite the bullet and learn > scary Node or try to keep it simple and find a way to save files without > going insane with browsers that are intent on making themselves pains in > the you know what. I see a few threads that suggest there may be a way > forward for us file users but I'm wondering what to do for the next few > months and then I'm wondering if I should just bite the bullet and move to > Node. > > So Use Case 1 (work): > > Use FF file:// to author content, scp to an Apache server, company sees > the content via http. > > So Use Case 2 (personal): > > Ideally create an multi-user authoring solution that would allow users > (and myself) to author content that I could deploy at my own URL via a > hosting service. The idea here is to "write" a collaborative piece of > fiction with potentially many disparate paths... the ultimate interactive > story experience essentially. > > Alternatives to Use Case 1, just accept that Google Docs and Wordpress > have won the day at work and stop making things hard for myself. > > Alternatives to Use Case 2, just write my novel in Word (OK OpenOffice) > and die an agonizing slow death. ;-) > > Looking for guidance... point me in a direction or two and then I'll go > away for another decade. > > Thanks. > -- 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/740ad119-932d-41ae-af12-00d486f1f858%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
