Hi Rich, > I did some preliminary research and found this page from Google > <https://developers.google.com/admin-sdk/groups-settings/downloads>,
not sure if that helps though. > Not at all, it is an API for groups "settings" only... https://developers.google.com/admin-sdk/groups-settings/v1/reference/groups > In Classic TW you could create several broken up TW and bring them > together in one. > If your envisioned end-goal is to bring them together then it doesn't matter if they were stored as different tiddlywikis. You are thinking of bringing a big lot of individual Wiki's together in one TiddlyWiki and it's literally impossible at that scale. Just halt there for a second and imagine your browser asking google to "give me all TiddlyWiki posts, now", since 200X. You see where we're headed? It's a place called nowhere. So I guess that is another question at what point is a TW dataset too big > for a single HTML file > and can TW5 do that same Classic Trick of creating many small TW5's that > feed a main TW5? > Support for that in TWc is rather limited and the kind of support there is actually makes one big TiddlyWiki out of it. The point is getting ready and working on what we can so we are prepared > when we have something 'federated'. Federation does not mean replacing the google groups. It means an ability to work together in a well defined context, like a singe google groups thread, perhaps a more or less small project involving a handfull of threads. It also helps get things started for federated TW by looking at a problem > that would directly use it. Yes, but the way you do this is *not* by starting with the motherlode. > Or better said as a question, How do we deal with Nested Multiperson discussions? Now we're getting somewhere, so... 1. find a solution for a multiuser environment with TiddlyWiki - see how quickly we arrived at server-land? 2. see if you can establish something like nested discussions - also server-land in terms of making efficient queries ...in that order only. Take away the federation for a second, > I am talking about simply inside a TW5, > how would you show a forum post? What is a forum post without a forum? ...but a circumcised archive with unsutable markup on top. Otherwise ...you would do that by importing / syncing the newsgroup with some filesystem replicating it. Then you would have a big mess and even less than google groups and no collaboration. Is there a better way to handle 'threaded' material than what we already > have the ability to do? Not in TiddlyWiki, otherwise we'd be using it. You brought up a point I was unaware of that there is no server side > node.js search, > then how do you search with node.js TW then? Either by using TiddlyWiki as the file that gives you interactivity... and node.js rendering it. Or by using things like google search or duckduckgo with your static files, or using something like tipue <http://static.tiddlyspot.com/#Search%20Via%20Tipue>... for a single manageable wiki only, however, not for what you call a "forum" like google groups. Here is an exercise and what got me to start thinking about this issue in > the first place. > Take one small thread(3 - 5 posts) how can we work with that single issue > data set inside TW5? You could use something like taggly tagging to achieve that, in TiddlyWiki. That would require all the posts from the thread already being loaded. But, again, we are talking Big Server here, if you want a multiuser forum. So, forget how TiddlyWiki works for a second and look at server-sides. If anything, only tiddlyweb is capable right now to provide both the store and search api right now. This post was and is to explore exactly where our issues are besides > 'federation' and to start plugging the gaps we can. Yes, but the gap is not one from "no federation" to "google groups". If that is your defined gap, then it makes it difficult to take steps. > I saw the gaps with > 1. Getting the data and figuring out how to work with it. > 1a. There might be some magic plug in that would allow us to view google > group data inside TW for all I know. > I'm afraid, that's not how such projects work. You start with simple, manageable chunks. We're not in data-mining land, we're in interactive collaboration land, with workflows and processes, not just unshakeable data that just sit somewhere. So, we start blank, then we accumulate data and if things go awry, we start fixing the little things. We don't start by dumping mountains of tiddlers in a pond expecting to find that one tiddler better, just like that. I mean, if some data-mining expert would provide an even more powerful tiddlyweb api, ok. But all of that is outside the scope of TiddlyWiki, imho, insofar as TiddlyWiki would only be the place to show the stuff, but not at all to actually store all that... or to make it accessible via queries. > 2. How to view and work with this data inside TW5. Therefore, if you want a forum, TiddlyWiki pretty much needs the kind of adapters for syncing it already has, plus the missing, server-specific search adapters. But, most importantly, it requires a server-infrastructure able to handle the load that currently hits the google groups. Best wishes, Tobias. -- 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.
