web commit by http://id.inelegant.org/

[git.ikiwiki.info.git] / doc / index / discussion.mdwn

diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index 05b034026d31aface6b70766a37bfc97e8c8c87e..f15d91c6d3615d7b63fd6134b8420b7a890ef4e7 100644 (file)
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -117,7 +117,7 @@ actions.  However, it may not be something everyone appreciates.  Any thoughts?
 --[Mazirian](http://mazirian.com)
 
 > Maybe, although it would need to take the critisism at
 --[Mazirian](http://mazirian.com)
 
 > Maybe, although it would need to take the critisism at

-> http://www.cs.tut.fi/~jkorpela/forms/accesskey.html into account.
+> <http://www.cs.tut.fi/~jkorpela/forms/accesskey.html> into account.

 
 >> Thank you for that link. Given that the edit link is the first thing you tab to
 >> in the current layout, I guess it isn't all that necessary. I have had a 
 
 >> Thank you for that link. Given that the edit link is the first thing you tab to
 >> in the current layout, I guess it isn't all that necessary. I have had a 


@@ -147,16 +147,6 @@ Ok, that's my last 2 cents for a while. --[Mazirian](http://mazirian.com)
 
 ----
 
 
 ----
 

-# RecentChanges should show path to wiki sub-pages?
-
-The RecentChanges only shows the final file name for the recently changes file,
-for example "discussion". It would be more useful to see "index/discussion"
-or the path to the sub-page. I think this is handled by the htmllink() routine.
-
-> Went ahead and did this, IMHO the display is ok as-is. --[[Joey]]
-
-----
-

 # Should not create an existing page
 
 This might be a bug, but will discuss it here first.
 # Should not create an existing page
 
 This might be a bug, but will discuss it here first.


@@ -175,20 +165,26 @@ Clicking on an old "?" or going to a create link but new Markdown content exists
 
 ----
 
 
 ----
 

-# Refreshing RecentChanges page
+# User database tools?

 
 

-What do you think about refreshing RecentChanges page (via Meta Refresh Tag)?
-It can be useful for users like me which rather prefer watching the last changes
-in WWW browser tab than subscribing to page. --Pawel
+Any tool to view user database?

 
 

-> Depends, if it were done the time period should be made configurable.
-> Unwanted server load due to refeshing could be a problem for some.
-> --[[Joey]]
+Any tool to edit the user database?
+
+> No, but it's fairly easy to write such tools in perl. For example, to
+> list all users in the user database:
+
+       joey@kodama:~/src/joeywiki/.ikiwiki>perl -le 'use Storable; my $userinfo=Storable::retrieve("userdb"); print $_ foreach keys %$userinfo'         
+       http://joey.kitenet.net/
+       foo

 
 

->> Yes, it should be configurable by ikiwiki admin. I believe he's not
->> stupid and he will not set too short refresh period to kill his server :)
->> I propose to add `recentchanges_refresh` variable in ikiwiki setup
->> to setting refresh period. If it's not defined, then ikiwiki doesn't put
->> refresh meta tag into `recentchanges.tmpl`. Do you like it? ;) --Pawel
+> To list each user's email address:

 
 

->>> Seems reasonable --[[Joey]]
+       joey@kodama:~/src/joeywiki/.ikiwiki>perl -le 'use Storable; my $userinfo=Storable::retrieve("userdb"); print $userinfo->{$_}->{email} foreach keys %$userinfo'
+       
+       joey@kitenet.net
+
+> Editing is simply a matter of changing values and calling Storable::store().
+> I've not written actual utilities to do this yet because I've only needed
+> to do it rarely, and the data I've wanted has been different each time.
+> --[[Joey]]