Arlen Beiler

So are we just doing buffer in this PR and then stream in a different PR? Do both PRs get merged?

@Jermolene I know this idea got hijacked by that other suggestion which I won't link to for fear of getting more people involved in this again. This one feature is...

In the particular case I am working on, whitespace trim did not fix the problem.

Although #4290 may be of interest to many, as a structure developer rather than a content developer I am very keen to see this feature made optional. It has been...

> We could use `text/tiddlywiki; content` and `text/tiddlywiki; structure` for the two content types (which is valid content-type syntax) and add them both to the list. Actually, this is incorrect....

The one thing I don't like about this is the way it crosses the parser with the widgets. That's not actually supposed to work that way. There is no way...

As a no-op function, it would be implemented by a plugin with the same goal as https://github.com/Arlen22/TW5-storage-plugin, which is to make TiddlyWiki "client-side" data folders that are compatible with a...

The reasoning behind this idea is simple. Without this feature, a "client-side" data folder would need to be loaded in its entirety on every request, which is a very disk-intensive...

I should have tested before creating the PR. It doesn't work in boot because utils-node isn't loaded until later. A plugin needing this functionality would just use `th-server-command-post-start` to do...

I'm studying the filesystem code and I think I'm going to add an additional stipulation to `$tw.utils.generateTiddlerFilepath` that the filepath must be under the specified directory. In other words, client-side...