Brion Vibber wrote:
Luis Casillas wrote:
Ooops, accidental send. What I meant to ask is whether there is some intrinsic design characteristic that makes it unsuitable for such use, or whether it's a matter of implementation details that development doesn't address because the software is not intended for that.
While it's possible to hack in some more access control, the wiki is designed to assume that all pages are always *readable*. The existing read whitelist is an unsupported hack and I guarantee there are holes in it.
If someone wants to use our software for something where there may be legal liability in allowing unauthorized people to access material on the wiki, they do so at their sole risk and are responsible for finding and plugging any holes in their system.
The best way is to put the restricted material _somewhere else_ and reference it, or to use HTTP authentication to restrict access to the entire wiki.
Or one can join the development team and implement a real restriction system :o)
You will be most welcome to do.