Recent blog entries for cdent

If your firewall is configured to block PUT or DELETE TiddlyWeb will have a very hard time doing the job is was built to do. If you are in this situation first try asking your firewall administrator to make a change. PUT and DELETE are legitimate and common parts of HTTP, they should not be blocked, they pose no greater risk that POST.

If that doesn't work there are some plugins that make it so PUT and DELETE can be tunneled over POST. You will need:

• tiddlywebplugins.methodhack
• Code like the plugin found in methodhack which overrides jQuery AJAX calls.

Note that this code has not been extensively tested as the number of crummy firewalls with bad rules is thankfully decreasing.

in reply to DentBook:

or at least start writing some draft-chapters tiddlers

Well yeah, but who's going to provide the time?

Pushed out TiddlySpace 1.1.1 which is primarily a merge of the bengillies reply code into core. I'm hopeful that this is one of the more important changes to TiddlySpace.

With prompting from fnd updated tiddlywebplugins.markdown to linkify bare http and https links.

Moved tiddlywebplugins.wikklytextrender to its own repo. Since it is still a default part of TiddlyWebWiki this seems to make sense, even though there are more effective rendering options now.

Moved tiddlywebplugins.methodhack to its own repo as well. With any luck, nobody needs to use this plugin anymore as these are more enlightened times. Ha!

in reply to test 2:

dolor sit amet

Solutioneer preponderonce damn these electric pants facilitate douche. My razor sharp parting or is political correctness gone mad verbificate ironic facial hair. Manifest rhubarb your mailbox quota has been exceeded follow my razor sharp parting. Manifest our leverage social media facilate stout and sensible shoes. Fixie never and fiercly proud of it cache douchebag.

Courtesy of http://douchebagipsum.com/

in reply to TiddlySpace 1.1.1:

I'm very pleased that the reply functionality has been moved into the core of TiddlySpace. Done well it will increase the amount of interaction and discovery in TiddlySpace.

Now that reply is available by default in a TiddlyWiki, should be make the reply button show up on the HTML rep by default?

This release moves the reply functionality into the core, making it a default behavior.

Like hayfever and stuff.

This release removes the "apps" app as the entry point to a new space. It was not suitably guiding for new visitors.

I'm in the process of releasing and deploying TiddlySpace 1.1.0.

in reply to local Gemfile:

warn "\e[1;31m" + "[WARNING] using Gemfile.dev" + "\e[0m"

What is it with the doucheoisie and their need to ansi escape?