This tiddler makes an effort to record architecture and conceptual missing pieces in the TiddlyWeb (and by extension TiddlySpace) ecosystem that may be necessary for penetration. It's by no means complete.

Somewhat Important

• Proper documentation.
• Properly inclusive project website.
• l10n and i18n.
• oAuth (2) as both a client and a resource {owner,server}. This is required to be a part of the interconnectedness of the web that respects identity and privacy (somewhat)
• SSL for at least authentication (challenge) transactions, if not anything with an auth token.
• Proper free text search (see SearchShortcomings).
• Metrics (what gets read and writ, who does it, etc).
• tsapp and related tools.
• Effective deployment and management strategies for auxiliary tools like twikifier and twsock.
• Web-based administrative tools (looking forward to seeing what comes of TSPolicymaker).

Maybe Important

• Facebook Connect and Sign in with Twitter (and similar).
• Better binary tiddlers
• An interface which shows available tags in some collection.
• Make remotebag a useful tool.
• Make PuSH relevant.
• In TiddlySpace solve for the AuxBags problem.
• In TiddlySpace make Bring Your Own Domain available to real users.

See Also

Older related things:

• TiddlyWorkWants
• TiddlyWorkNeeds

Bug fixing and continuations of yesterday's efforts.

Released TiddlyWeb 1.2.61.

Wrote up some thoughts on TiddlyWeb Missing Infrastructure. Would be great if people provide their own thoughts on the matter.

Remove unused modules from the apache2 configuration on tiddlyspace.com.

More work to get large tiddler PUT and DELETE to be more efficient when using tiddlywebplugins.sqlalchemy3.

Wrote to google groups about binary tiddlers in tiddlyweb.

Looks like the country might deserve an asbo on the jubilee.

Blocked bots from indexing revisions via the default robots file.

I looked into updating nodejs on tiddlyspace.com to see if it would address problems with twikifier but discovered that I couldn't update node without updating a bunch of the npm installed modules: Changes in APIs. Given the time constraints this evening that was more than I was willing to contemplate, so some other time. It does point out, however, that both twikifier and twsock need to be packaged in a way that allows for easy deployment (like TiddlySpace itself).

Spent some time experimenting with allowing the text attribute of a Tiddler object to be a file object to see if this might be more efficient when dealing with binary tiddlers. Unfortunately the change does not address the recently raised JSON PUT of binary data issue.

To address both the incoming HTTP socket's filehandle needs to be carried around throughout the current request. This could allow binary content to be written straight to disk from the socket, without going into RAM.

However, getting this to work without making changes throughout StorageInterfaces and Serializations is likely hard. Of course that's speculation. It could be spectacularly easy, but the concern is to not impact existing code too much.

Perhaps a Tiddler subclass could be useful? More poking required.

At the same time I did some analysis on the sqlalchemy code to see if I could locate where problems with PUT and DELETE may be coming from. For DELETE there were issues with loading too many objects into the session. Still unclear on PUT.