IntimacyGradient

MeatballWiki | RecentChanges | Random Page | Indices | Categories

found this over at SocialText - talking about public / private not being the right question. I am not convinced and wonder what others think about this idea.

Is there a simple way to implement a public / semi-private / private wiki?

http://www.socialtext.net/exchange/index.cgi?intimacy_gradient

: I think that you don't have to implement it specially, it's implemented in the people who use it. The general public is just not following RecentChanges and looking at every little page that gets created. People who take their time to do it and are interested are in the "semi private" area. Pages also have different "feel" of privacy, depending on what they contain. Pages like RecentVisitors or MessageBoard are edited easier than, say, long pages in document mode. Using the metaphor from Christopher Alexander's patterns, you don't usually lock your bedroom, your guests have enough common sense to not go in there on their own. -- RadomirDopieralski

> A small group of us have been testing a simple "PrivacyHack?" that "hides" the bulk of an OddMuse wiki, leaving just one of the site's namespace folders visible (unless you have accepted a password "cookie". While this is very simple to implement, the problems of managing the passwords has been found to be "not so simple". I know that many of the more sophisticated WikiEngines (especially those designed for corporate use) have elaborate permission systems that create simpler ways of maintaining "permissions", but I also believe this comes at the cost of significant additional software maintenance burdens. In short, I have yet to find a "simple way" to achieve even a few levels of privacy. -- HansWobbe

IntimacyGradient

Discussion