Will external tiddlers be saved together with the original tiddlywiki?

#1

I am trying to understand the concept of “external content”, that is, transcluding selected tiddlers from another tiddlywiki. I have noticed this plugin Saq's Sandbox — Experimental doodads but I don’t know if and how to use it (it mentions something about hosts with CORS support…).

Anyway my use case is the following: I’d like to present some content in my Tiddlywiki online but I don’t want the users to be able to save it for offline use. Because even when there are not supposed to do Ctrl-S, people will still do it and get a some version of the whole wiki, sometimes fully functional.

So I was thinking to transclude the content that I don’t want to be saved locally from another tiddlywiki, expecting that this way I would prevent saving the external content together with the “mother” tiddlywiki. But maybe I am completely wrong and there is no solution for my use case.

Thank you for any possible direction in this.

AS

1 Like
#2

If other users can access it at all, then they can find a way to vacuum up the data…

Certainly, I have an automatic external tiddler import that I use (when I’m logged in via tiddlyhost), but which ordinary web visitors cannot use. Then I can see external tiddlers that the visitors cannot see. But then they’re not even seeing it…

But if your intent is to display external stuff as tiddlers (for web visitors other than you to see), I don’t see any way for those tiddlers to be viewed and yet shielded from getting exported. Of course, they can be removed from the publish filter, so “save” doesn’t get them. But it sounds like you want an ability for visitors to see the external (imported) tiddler data, without any kind of copy…?

Maybe say more about what your workflow is, how other users are accessing your wiki, what level of security you’re seeking…?

#3

Maybe you’d be interested in my demo / explanation of external tiddlers here, including clarification of how to modify the publish filter.

#4

Other alternative may be to use a tiddler level encryption.

Regardless it is hard to take an open source solution and without an authentication or server make it somewhat closed. Perhaps you need to use another method to access the content of the private tiddlers that itself demands authentication to see them at all.

#5

use html tag “iframe” to embed another tiddlywiki generated static page.

#6

Right, that can be the best approach for some use-cases. Still, if someone downloads the whole wiki, they’re going to see that iframe, and have exactly the access to it that they had via the web interface…

The benefit of importing tiddlers is you get all the interface integration (links, templates, search results, etc.) corresponding to those tiddlers.

Until we know more about what OP’s (@ Albertina_Scotti’s) needs are, it’s hard to know what kind of “transcluding selected content from another tidlywiki… presenting content” is needed, and what level of protection from copying/downloading is called for.

#7

Thank you all for your valuable input, I knew from the start that what I want is probably impossible. It’s like with any html/web browser related stuff - once you see it, it means you have downloaded it and you have it stored locally (even if you don’t realize it). That part, I think, I understand.

I was just hoping that by using the Saq’s plugin (or something else) I would prevent storing the content which was not loaded/opened/seen yet. The main reason is that I have a lot of content that is “hidden” behind links and transclusions (like terms in a dictionary) which does not need to be loaded and then also potentially saved (if the user does manual save like with Ctrl-S). My “hidden” content is often as big as the main content but it’s rarely opened.

Now I am aware that I did not describe my needs correctly to begin with, my fault. I will try to understand how to use ExternalContent Plugin by Saq.

AS