Hi Mat, I myself have Node configured to *not *lazily load tiddlers (which seems to be the default), but I *think* you can tell the Node version to lazily load images in this case. However, because of the limitations, I personally avoid adding large files like images or PDFs to my wiki - I'm still looking for a solution to this problem!
Currently, I do one of the following: - Add a tiddler with _canonical_uri - Add a link to the document - Add a snippet of text "located at $FILEPATH on $COMPUTER name" These all have the some problem in common - the document could disappear! That's less of a problem for the third one, but my backups could still go bad and I could lose access to the document. Not to mention, that last solution loses me access if I'm not on the computer I stored the document on. I was thinking of looking into some "distributed filesystem" technologies like IPFS or Dat for this, but the need hasn't been pressing enough. If anyone's got experience with these kinds of technologies (especially used in conjunction with TiddlyWiki!), I'd love to hear your thoughts on the matter! -Rob On Wednesday, May 20, 2020 at 12:46:36 AM UTC-5, Mat wrote: > > Question to the TiddlyWiki on Node.js users: > > Are tiddlers lazily loaded? > If yes, does this mean that there is no problem with directly embedding > big content (e.g images)? Or is it the same limitation as with single file > TW? > > Thx > > <:-) > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a653fac6-033f-4b3f-a269-c949b286f7c4%40googlegroups.com.
