There are at least two challenges with what you call "nameplates":
1. you need a decent "predefined" standard format the communuty
subscribes to / adopts
2. you actually want your "imported" nameplate tiddlers to auto-update
- otherwise it's going to be difficult for you to know when your info
is outdated
So that leads to a really good question, how do you protect things in
> TW5verse if you don't want it consumed?
>
Can you block the drag and drop of data?
>
Actually, not (easily) consumable to me means: Not exposing to the outside
world (without encryption). So, if something is drag and dropable it is
sure consumable. Whether it is optimized for sharability like a plugin is a
different issue. Anything you can easily see in your browser or see get in
your preferred source-code-viewer is consumable to me.
I find the drag and drop of Tiddlers to be one of the strongest TW5
> features. Not many things have this ability and none at the level of TW5.
> As they often say, 'That is not a bug, it is a feature' and in this case I
> feel that phrase fits TW5 drag and dropability very well.
>
So, yes, definitely a feature. However, if you desire for things to be more
of a shared nature, you not only need some ad-hoc swarms that make it easy
to grab things but actual, versioned packages of stuff... or else you will
never know what to update and from where. So, you will have to leave it to
the author(s) of content as to what degree they offer packaged stuff for
"batch-consumption".
In social networks you might be able to track back 1 maybe 2 levels.
> Wouldn't it be cool if you could easily track back a TW5 Tiddler all the
> way to the start.
>
Todays "social networks" know little of content updates... unless you
consider GitHub to be an actually decent social environment.
So I drag and drop a Tiddler by Tobias, then 5 other levels do the same
> thing and you can still tell that Tobias created this and it traveled this
> path to get to another page.
>
There is a lot of (trouble) involved in this. After all, the things you
wished to grab might...
- not be from me
- partially exist in your wiki
...just to name two.
> I think this is very important for the long term of social data sharing no
> matter what platform, who grabbed what and shared it with who.
>
Indeed, not sure how "social encapsulation" could work so that TiddlyWiki
shows you the original titles whereas — under the hood — they are actually
stored as "origin — title". Imagine there being a "virtual store" in the
context of which that social content is run, if that's understandable, e.g.
a filter run in a "social tiddler" runs against the social store of the
remote repo rather than your own. That way it will have integrity with
whatever you've imported ...but not with your stuff, right away that is.
I will explore the iFrame option for the hangouts to point to people's site
> for their bio data.
That way if they update their site that will automatically update to my
> site.
I would think that, at the moment this is the most sensible approach, even
though you end up loading entire tiddlywiki's just so you can display a
"nameplate".
Best wishes, Tobias.
--
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.
