X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/a436a80c08726bf7c97c59ff59686c4808ced3f6..fb2c3ab3b5e6c9bade718394960bda20e408715d:/doc/index/discussion.mdwn diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index 351122063..6987c2f4e 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -11,7 +11,7 @@ Note that for more formal bug reports or todo items, you can also edit the I just figured I'd edit something on the page with my OpenID, since you've implemented it! --*[Kyle](http://kitenet.net/~kyle/)*= -> Kyle, If you like openid, I can switch your personal wiki over to use your openid --[[Joey]] +> Kyle, If you like openid, I can switch your personal wiki over to use your openid. --[[Joey]] ---- @@ -27,6 +27,19 @@ something, that I think is very valuable. > overwhelming desire to work on myself right now. Patches appreciated and > I'll be happy to point you in the right directions.. --[[Joey]] +>> I'm really curious how you'd suggest implementing ACLs on reading a page. +>> It seems to me the only way you could do it is .htaccess DenyAll or something, +>> and then route all page views through ikiwiki.cgi. Am I missing something? +>> --[[Ethan]] + +>>> Or you could just use apache or whatever and set up the access controls +>>> there. Of course, that wouldn't integrate very well with the wiki, +>>> unless perhaps you decided to use http basic authentication and the +>>> httpauth plugin for ikiwiki that integrates with that.. [[--Joey]] + +>>>> Which would rule out openid, or other fun forms of auth. And routing all access +>>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]] + ---- Some questions about the RecentChanges function. -- Ethan @@ -58,4 +71,4 @@ with all news or the one with the latest news only, I don't know yet.) >> That wouldn't use the same style for the RSS and Atom links, and it >> wouldn't embed the feed link into `` so that browsers can automatically ->> find it. \ No newline at end of file +>> find it.