Apologies for the late reply, this got buried in my backlog while I was away for a few weeks during the holiday season.
This is not quite accurate, the FileUploads plugin introduces Uploader modules that interface with the backend where the files are supposed to be saved. The Uploader modules are independent of savers and in fact do not interact with them due to core constraints. More details on how these different parts relate to each other, and core plans to reduce duplication and increase reusability in this area were discussed in the community call of August 17th, 2021 which I recommend revisiting.
Posting requests here is OK, though they should be addressed to the wider community rather than to me personally. FileUploads is a Commons plugin - rather than something I am personally responsible for - and as such further development is driven by community consensus and support.
The process for trying to add support for a new backend uploader looks something like this with the Commons model (in no particular order):
- the community finds a developer willing to work on it.
- assess if the backend is viable to write an Uploader for.
- the community provides support for their work if needed via OpenCollective.
Some background that might help in understanding the processs:
I volunteered to work on the first version of the FileUploads plugin and the Fission uploader, and my work was partially supported by community funding via OpenCollective. That work has been completed. There is a grey area of providing supports for bugs and maintenance as the Commons model evolved as we worked on it and was not originally discussed, I am volunteering to provide support for bug fixes for the FileUploads plugin and FissionUploader for the near future.
The development of this plugin and the Commons is in part an experiment to try and find a sustainable model for community driven TiddlyWiki development. As such, there is a strong preference that in order to gain greater insight and experience in the process, we involve other community members and developers to work on future backends. We currently have two backends that we are collecting funds for on OpenCollective and are looking for developers for:
On Timimi:
I am not familiar with this saving method nor does it align with my personal interests - I strongly prefer WebDAV for local saving of single file wikis. I had a quick look to try to ascertain the feasibility for creating an Uploader that works with Timimi. My first impression is that this would require a significant rewrite of Timimi itself as it does not seem to support saving arbitrary files to specified locations. This would therefore be a larger piece of work than just writing an Uploader for a backend that already has the requisite support/API that we can work with, something to keep in mind when looking for a developer for this work.