Hi again Birthe, > I wonder how it will cope with many users. I think it would be best for > public topic-specialized wikis to fetch links to plugins, as you suggest. > I recall the problems we had with TWclassic. Lots of modified versions of > the same plugins around. The good part is that most users will get to know > TWederation. I think many people are collecting links, writing tips and > tricks for themselves to remember and reuse later on. It is done in native > language, and the way we ourselves understand it. The quality will vary of > course, but it can be shared. Beginners and simple users like myself are > the ones needing it the most, and everybody would be able to find stuff and > start creating stuff for sharing. We decide ourselves what we want to > share, and what we want to fetch, but some kind of evaluation system would > be good. >
Yes, we'll need a way to keep track of versions. If I recall, this is already in place with a kind of UUID both in Jeds and Jeremys variants. But I think that you'll only fetch from a few sources which will work as some kind of quality system. Also, if I recall my conversations with Jed, we talked about trackability and how to make the original source also be part of the meta-info in a tiddler. It's something we'd have to experiment with. > Any thoughts on structure? The TWederation we tried used twCards for > identification. Nobody would like to fetch everything from everyone. Would > we need lots of different twCards? I realise filters can be used, but it > needs to be easy enough for a beginner from the start. It really has to be > easy to start finding the topic-specialized wikis, From there it will > spread like rings in water. > First, much of what I say about TWederation is just my vision of things. Of course, much of it already is possible even with the current TWederation version, but would still have to be built, like a "plugin list". This also means that how things will/can work is up to the individual federated networks and their participants. The transferring fetch-mechanism is one thing but what people build based from it is another, just like TW at large. We would need some way of identifying sources so, yes, twCards make sense. As for finding the topic specialized wikis, there are a few imaginable variants. The simplest is probably that a few are already build in, just like the plugin library in vanilla TW has the source build in. > Sorry to be dense but I do not understand everything in English. > Heh! It sure seems like you understand everything. <:-) -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3e2e10cd-af8a-4a4a-9712-24a6d3930375%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
