This is a temporary note taking tiddler related to possible tasks to improve TiddlyWebWiki. See also Futures where there are additional ideas.

• in wiki login?
  
• more effective handling of 412
  
• fixing (for real) the Error "OK" thing
  
• add plugin based handling of the new server.content-type field
  
  • (such that you can't edit a binary?
    
• confirm/make real etc visibility of different permissions on different tiddlers
  
• catologue the ways in which on demand loading fails to be complete
  
• if its not already been fixed, deal with those weirdnesses in sync that I pointed out a while back but can't really remember now
  
• forget about Martin and fix the diff thing yourself
  
• spend some time linting and pep8ing tww code, just for sake of review and refresh
  
• continue work on a tww+recipes+bags expose
  
  • i.e. some docs
    
• consider adding a help/about (bag and recipe) or (tiddler) to tww distribution
  
• decide when/where/how a proxy is going to fit in
  
• figure out where the sync UI breaks when there are too many tiddlers (this is something discussed with JR early on)
  
• detune server.workspace back into _just_ the sync machine, and not the twww.serialization
  
• add a plugin which strings a callback on the back of any request to server.host which does a GET of recent tiddlers on the workspace/recipe/bag modified since the last time we checked (based on locally stored javascript variable, instantiated at load time). if there are changes, notify somehow
  
  • (that's another thing that was discussed in various forms in the past