X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/cc511f51312a0b86da1c869fcc6532d299ad5f64..2a55084f746d0410cb75364e3b9370f7a2b61d50:/doc/index/discussion.mdwn?ds=inline diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index bba3110cd..6987c2f4e 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -5,6 +5,14 @@ Do so here.. Note that for more formal bug reports or todo items, you can also edit the [[bugs]] and [[todo]] pages. +---- + +# OpenID + +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]] + ---- # ACL @@ -19,16 +27,48 @@ 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. +Some questions about the RecentChanges function. -- Ethan + +> (Moved to [[todo/recentchanges]] --[[Joey]]) + +---- -* Why isn't it statically-genereated, but generated dynamically by CGI? It seems like it could be beneficial to have it rendered in the post-commit hook, just like everything else in the wiki. -* Also, is it planned/desired that recent changes generate the same information in RSS feed format? This seems like it could be a useful way to keep track of the wiki as a whole. -* Lastly, would it be possible to use the recent changes code with a pagespec? I understand this sort of infringes on territory covered by the inline plugin, but the inline plugin only puts a page in the RSS feed once, when it's created, and I imagine some people -- some deranged, obsessive-compulsive people like myself -- would like to know about the changes made to existing pages as well as newly-created pages. +Also, I'd like to request another template parameter which is just +$config{url}. That way you won't have to hard-code the URL of the wiki into +the template. -- Ethan -Thanks for your time. -- Ethan +> That's already available in the BASEURL parameter. --[[Joey]] ---- -Also, I'd like to request another template parameter which is just $config{url}. That way you won't have to hard-code the URL of the wiki into the template. -- Ethan \ No newline at end of file +# Canonical feed location? + +Any way to use `inline` but point the feed links to a different feed on the +same site? I have news in news/*, a news archive in news.mdwn, and the +first few news items on index.mdwn, but I don't really want two separate +feeds, one with all news and one with the latest few articles; I'd rather +point the RSS feed links of both to the same feed. (Which one, the one +with all news or the one with the latest news only, I don't know yet.) + +> Not currently. It could be implemented, or you could just turn off the +> rss feed for the index page, and manually put in a wikilink to the news +> page and rss feed. --[[Joey]] + +>> 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.