Jed Carty wrote: > > I tried to start a listing of plugins that I was hoping to extend to other > tiddlywiki resources that is similar to what you are describing but then I > got distracted and I don't think anyone else really started using it. What > I made is here: http://inmysocks.tiddlyspot.com/#Plugin%20twCard >
With the risk of sounding patronizing: A main idea is of course that individuals should *not *do those kinds of things - for the exact reason you state; we get distracted. Instead, that list ought be built by the central server, listing all fetched tiddlers that, say, have the tag "Plugin" (or, probably better, some form of meta-data tiddlers that extract data from fetched plugin tiddlers and then ditch the actual plugin tiddlers). The idea is to set it up so that you can use the same filters as in our > implementation of twederation and get just the tiddlers back instead of > loading the full wiki. So it would take much less time and would let you > get tiddlers from multiple wikis if they are on the server and it would be > much faster than the non-server assisted way. > >From where would I actually fetch the tiddlers - from the actual wikis or from the central server? Because if it is from the actual wikis... then how do I extract individual tiddlers, and if it is from the server then will this mean the server will continually collect *and keep* copies of the *full *wikis? Or would the server fetch the wikis on demand and splice out the tiddlers that I can then fetch... which would not be fast. Or maybe the server only keeps copies of tiddlers subscribed to as specified by e.g tags or some subscriber-defined filter... "subscribe to [tag[@mat]has[bar]]"... You could set up something that serves wikis like this without ssl but I > wouldn't trust a system for editing the wikis online without https. If I recall, there was some conflict that http wikis could fetch from both http and https, but https wikis could only fetch from https. But was there also some issue that the current TWederation implementation could not handle https? ...or was that only because it was hosted on tiddlyspot (http)? Other than as a generally good tip, I am unsure how this relates to what we're discussing (and I don't mean that it doesn't, I just mean that I don't understand). <:-) -- 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 https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/9cf003ee-c9fd-4306-b6ec-77b02080b870%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
