It is working for me, I tried to find ways to break it and I haven't been 
able to find anything other than it doesn't try and download tiddlers that 
use _canonical_uri fields (you can just download them directly from their 
location, I may update it to download them in the future).

It shouldn't be limited to working with Bob or node, the behaviour is 
completely in the browser.

There may be some browser setting that prevents it, but I am not aware of 
anything that would do that.

The types it downloads are limited to 'image/gif', 'image/x-icon', 
'image/jpeg', 'image/jpeg', 'image/png', 'image/svg+xml', 
'application/pdf', 'application/zip', 'application/font-woff', 
'application/x-font-ttf', 'audio/ogg', 'video/mp4', 'audio/mp3', 
'audio/mp4' because those are the ones I thought of at the time. It won't 
work if the tiddler doesn't have one of those types. Eventually I will 
probably add a setting that lets you change the list of mime types it will 
download.

It also will not try and download images that are included using 
_canonical_uri, the plugin will take tiddlers that are base64 encoded and 
try to download the non-base64 encoded version.

On Wednesday, September 4, 2019 at 1:58:22 AM UTC+2, TonyM wrote:
>
> Folks,
>
> I believe there has being discussion of this in the past but just want to 
> ask if the ability to save/download binary tiddlers as files?
>
> Such as images, windows.lnk files, small exe's etc... 
> Assuming when imported no information is lost, we should be able to export 
> them as viable files?
> Understand there are security implications for Internet hosted binaries 
> but on internal, private ot local wikis this would be very helpful.
>
> Thanks for any info you may have
> Tony
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev/62f86fd1-f4c3-4128-9eec-b9dc14eb86ac%40googlegroups.com.

Reply via email to