Bureaucrats, developer, Administrators
9,854
edits
m (format) |
(amazing. i actually have something to blog) |
||
Line 1: | Line 1: | ||
Ok. This is a Blog, blog is just a web page where all the content is in reverse chronological order (kinda redundant: a blog in a wiki, but I'll see if this works). You may comment on posts if you like, but please be sensible and do it on the [[User_talk:Juxo/Blog|talk page]] | Ok. This is a Blog, blog is just a web page where all the content is in reverse chronological order (kinda redundant: a blog in a wiki, but I'll see if this works). You may comment on posts if you like, but please be sensible and do it on the [[User_talk:Juxo/Blog|talk page]] | ||
---- | |||
12.10.2003 | |||
Oh, the eternal incoherence. I guess I should merge [[The Consumerium Exchange]] and what is presented in [[User:Juxo/Thinking aloud]] into [[Wikinion]] but I'm sorta vary of it since it'll propably just create more incoherence and sooner or later someone might point out why it won't work that way either. | |||
Now if we implement this [[WikiVote]] thing then there are two or three different types of votes and three is too much imho. | |||
But the "new" [[Wiki]] approach and the [[features|original vision]] can be brought closer by using strictly named subarticles that are then "collapsed" into a viewable document for the [[consumer]] based on her/his [[preferences]] ie. articles and their subarticles form a tree and [[preferences]] define what branches and leaves are visible and in what order. If you want to see ecological stuff first when fine. If you want labor issues first, fine. If you want consumer reviews first, fine. And this way we can have more fine grained version control (signatures) and editors can concentrate on the subarticle that is closest to their expertese. Also newbie editors are less likely to get irrated over the syntax requirements that are not usually present in wikis. Parsing monolithic articles would require more performance. | |||
---- | ---- | ||
11.10.2003 | 11.10.2003 |