User:Jukeboksi/Chat Gallery/6.8.2005 with bumm13

[17:40] juxo> hey.. check out this cool (and little weird) wiki implementation. It's fully client side and uses Javascript for all the logic. It's very nice for a personal wikiwiki. There's only one HTML file, which you can put on a USB-memory and then have instant personal wiki anywhere you go
[17:40] bumm13> ok
[17:41] juxo> as long as you have a web client that does javascript
[17:41] juxo> http://www.tiddlywiki.com/
[17:41] juxo> it doesn't have "pages" or "articles", it has tiddlers (that are stored as <div>s in the single HTML file)
[17:42] bumm13> hmm, interesting
[17:42] juxo> note that it opens any "tiddlers" you click on "in-line"
[17:42] juxo> a very cool GUI
[17:43] bumm13> hmm
[17:43] juxo> I suppose it doesn't scale very well
[17:44] juxo> I'd definatelly use it if there were a conversion script to MediaWiki format
[17:44] juxo> on to other things..
[17:45] juxo> I've been thinking of this "sea of wiki" (or transwiki) approach to sharing pages among many wikis and minimizing the redundant manual work involved in such schemes
[17:46] bumm13> it's an interesting concept
[17:46] juxo> basically it works so that each article has a "master"-wiki
[17:46] juxo> if someone want's to edit an article that is "on loan" from some other wiki they will be guided there to edit it
[17:47] bumm13> hmm
[17:47] juxo> and any changes to the master wiki will automatically be imported to all the wikis using that page in their wiki after a delay
[17:47] juxo> say 30 minutes for a WP article
[17:48] juxo> if the edit sticks for 30 minutes it's not vandalism
[17:48] juxo> and if there is a revert within the timeframe, then both
[17:48] juxo> 1) the edit
[17:48] juxo> 2) the revert
[17:48] juxo> could be "wiped out" from history on the client wikis
[17:49] juxo> if that is desireable
[17:49] juxo> now this way WP could be rivalled or complemented (how ever you wanna see it) by a multitude of "specialist" wikis
[17:50] bumm13> yeah
[17:50] juxo> say if consumerium is the specialist in products
[17:50] juxo> and wikicompany is a specialist on historical developments of corporations
[17:51] juxo> and wikipedia is a specialist in encyclopedic information
[17:52] juxo> then each wiki could get their "filling" articles from other wikis dynamically and each wiki focus on what is their speciality and do good articles on those issues that are the core or essence of some wikis declaration of purpose to benefit all wikis
[17:53] juxo> naturally there should be the possibility that there can be a split in what is the master-wiki for some article
[17:54] juxo> ie. some wikis would keep WP as article-master while some sites go for the Wikinfo version
[17:56] juxo> every time I try to tell the MediaWiki people that there really is need for replicating articles from a chosen master-wiki they always respond with something like "Why don't you just redirect to WP?" which is annoying
[17:56] bumm13> yeah :(
[17:58] juxo> maybe WP itself has no need to use any other wiki as a master wiki for any article because WP is so complete and the information in there is usually meticulously complete but in operating a specialism-wiki (as opposed to WP being the generalism-wiki) this kind of functionality would be most welcome
[17:58] bumm13> sure
[17:58] juxo> There is the puny SpecialImport.php that no-one is actually developing
[17:59] juxo> and the whole export-import scheme (and application) of MW is really not developed at all
[17:59] juxo> One would instinctively expect that the Special:Import would automatically fetch desired pages from the other wikis, but no..
[17:59] juxo> you have to download via XML-export
[18:00] juxo> and then you have to upload to the Import-facility
[18:00] juxo> so there is no glue between the export and import "functionalities"
[18:00] bumm13> interesting
[18:01] juxo> I think it comes down to WP being Monolithic™ so they don't care about Fragmentic™ wikis at all
[18:01] bumm13> good possibility
[18:02] juxo> but the MW guys are also disregarding Wikimedia projects
[18:03] juxo> I think there isn't even one function in the codebase that is made to support Wiktionar(y)ies development
[18:04] juxo> I used to do english->finnish translations as therapy but then I got frustrated that after the wiktionaries were split up there was no brainstorming going on aiming to make a "TransWiktionary" ie. glue the disjoint wiktionries together
[18:04] bumm13> yeah, I can imagine
[18:08] juxo> but I really am in no position to whine about these if I don't get my stuff together and design a possible implementation framework (I do have some 4 yrs of CS studies, but then I dropped out) and present that to the MediaWiki-wizards
[18:08] juxo> erm..
[18:09] juxo> a workable design I mean by "implementation framework"
[18:11] juxo> I don't even know what is an "implementation framework", but it's just the sort of compu-speak that I've been listening to for years so I use it to describe something that is not quite pseudo-code, but that gives a sound plan (that a sw professional can follow) on how to implement features specified in an introduction to the problem(s) to be solved or new functionality to implement