*This has the promise to be a very interesting avenue of development for 
TiddlyWiki users, even for those not interested in using TiddlyWiki on 
Fission at the moment.*

A frequently discussed limitation with using TiddlyWiki is that embedding 
images and other files leads to very large and unwieldy file sizes. The 
basic idea here is to develop support in TiddlyWiki so that when you import 
an image or another file, it is uploaded to external storage backends 
(think Amazon S3, Webnative IPFS, Github pages, Google Drive etc), and just 
save a tiddler in the TiddlyWiki pointing to those files.

The workflow might look something like this:

   - configure your wiki via a settings tab in the control panel to upload 
   images to a storage backend of your choice that you have access to.
   - drag and drop an image to import.
   - the image is uploaded to your specified storage
   - a canonical_uri tiddler is created pointing to that image. 
   - You can now include the image in any of your tiddlers by just 
   including the canonical_uri tiddler. However, the image is not stored in 
   your TiddlyWiki and inflating its file size.

I've previously worked on a prototype of a plugin that does something 
similar for node.js and saves the images to the local file system. Thanks 
to Boris' support, I'll be able to dedicate the time to build on that work 
and the goal for the first version of this plugin will be to allow 
uploading files to Webnative IPFS when using TiddlyWiki on Fission. As far 
as possible, I will try to make the mechanism pluggable and usable with 
other storage backends, for which support can be added at a later date.

*By getting involved now, you have the opportunity to support and influence 
the design and implementation of this feature, as well as the 
implementation of support for other backends.*
Regards,

Saq

On Wednesday, May 26, 2021 at 9:33:10 AM UTC+2 [email protected] wrote:

> At last week's Fission Demo Day, Jeremy presented and we also announced an 
> initiative to build a plugin to support file uploads.
>
> Saq very quickly reached out, we had a chat last week, and confirmed that 
> he'll be leading the development of this as a core plugin.
>
> The initial features include:
> - create a new tiddler for each file
> - link the file using a canonical URI
> - resize images to create smaller thumbnails
>
> I've personally funded the Webnative IPFS backend as the first thing that 
> Saq will work on. Other backends / savers will be prioritized based on 
> backers. There's an option for company sponsorship at a higher tier, with 
> more direct recognition and promotion.
>
> We've got a discussion thread in the Fission forum: 
> https://talk.fission.codes/t/tiddlywiki-file-upload-plugin-webnative-ipfs-funded/1926
>
> You can directly contribute on OpenCollective: 
> https://opencollective.com/tiddlywiki-on-fission/projects/tiddlywiki-file-upload
>
> As a backer, your feedback, use cases, and feature suggestions are 
> prioritized. Your name and web link will be included in the README and 
> other communications around the plugin.
>
> As well as this plugin, I'd love feedback from you all on what you think 
> about this model? Can you help spread the word? Are there companies that 
> you know that would be interested?
>
> Also, if anyone is interested in coming up with a different idea for a 
> plugin or other TW related projects, I'm happy to help promote it and 
> support you in using Open Collective to reach your goal.
>
> For instance, I don't know who is in charge of the TiddlyWiki Discord 
> server, but one of the things we do in the Fission server is give special 
> roles to people who contribute to open collective projects, as another 
> piece of recognition.
>
> -- Boris
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7a85be5d-1f96-44d0-abdf-418f3b51c4d4n%40googlegroups.com.

Reply via email to