Erwan, thanks for your reply. Very interesting. Some thoughts arise:

I don't know how long a conversion from TW into TW node.js takes but the 
other steps you describe should be pretty fast if automated (right?).In 
other words, if the TWs were already in node.js form then this would be 
much simpler, correct?

But how about this for the twitter type idea, if at all possible; maybe 
it'd be enough to start off with looking at tiddler 
$:/core/ui/MoreSideBar/All 
<http://tiddlywiki.com/#%24%3A%2Fcore%2Fui%2FMoreSideBar%2FAll> and filter 
out the tiddlers that start with # and @. For twitter, you're not 
interested in all tiddlers, after all. Would this simplify/quickify your 
metod? 

Further, if your engine is included in the local wiki, it could look at the 
date for the last update and filter not only the # and @ tiddlers, but also 
only include those added or modified since last update!

BTW, I just posted a question 
<https://groups.google.com/forum/?fromgroups=#!topic/tiddlywikidev/7KxIAyLmdjc> 
on the dev group if it is possible to include a filter straight into the 
url which would be another approach for this. 

<:-)

-- 
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to