DomainBasedRealNamesFosterResponsibility because: * they are your verifiable OnlineIdentity * they signal that you are committed to your postings If you have written valuable postings in wikis, secure them with a * blog snapshot or a * copy in a Diigo annotation. -- FridemarPache '''Discussion:''' You can make your date-time-stamped Diigo annotations public or private. -- [http://www.fridemar.com fridemar] Could you refactor all these pages into a single page so as to create a compelling argument? Right now your points are fragmented, and consequently very difficult to understand. -- SunirShah Dear Sunir, the compelling argument lies in [http://domainsmagazine.com/Domains_2/Domain_4278.shtml the true economic value of wikis] and how to give each constructive peer a chance, to get a fair share of the generated value. Otherwise contributors of wikis are slaves, who work for zero dollars and lose the possible economic gains, that would allow them to realize a CommunityWiki:WikiWayOfLife. The usual arguments in wikis to suppress ecomomical thinking are: for your active engagement (if any) * you get so much inspiration and perhaps even enlightenment * you learn such a lot of good stuff in such a short time * you get so much intellectual pleasure by playing with new ideas * you make friends with such a lot of interesting people * you get (political) publicity * you get free expression * you train your language and communication skills * you learn how to argue * you get a very effective social filter for searching the web * .. That's true and we all appreciate that. But whereever you look in the wikis, you have the page maintainer problem. There are roughly two kinds of wikizen, who due to their "normal job" suffer, let me call them Underworkers and Overworkers. * Underworkers have not enough time to make the necessary "garbage collection" * Overworkers write large pages that at last become unmanagable too. There are not many people, who like to do the garbage collection for others. Yes, I could make a big monography of all the sketched ideas. That would take a year or so, but I think, I can do more for the community by offering small slides that can be expanded on demand. -- FridemarPache That's a fair point about monoliths being unexpandable, and not encouraging collaboration. Conversely, there is also the problem that if you offer too many current openings for engagement, a prospective engager won't know which one to take. Minimally, may I suggest making the page titles closer to pattern form rather than assertions. Our CamelCase is very hard to read when used in sentence form. Further, having a central ForwardIndex / RoadMap of what you're trying to achieve can provide some sort of map for a reader trying to jump in a few years from now. Regardless if you accept or reject such advice, I will try to keep up with what you're saying as best as I can. -- SunirShah Thank you Sunir for your engagement and your understanding. It is now 3:35 in the morning here in Germany and I must go to bed. After my sleep period I will read your recommended links. -- FridemarPache