1 I would like to allow comments on ikiwiki pages without CGI.
2 I have in mind something like
4 * Use a pagetemplate hook
6 * add a mailto: url to each page matching some pagespec
7 (currently every page gets a comment footer)
8 * this mailto url goes to an address identifying the page (something like
9 user-iki-FE653b@host.fqdn.tld). (DONE)
10 > I wonder if it would be more or less natural to put an encoded form
11 > of the page name in the email address? I'm thinking about something
12 > like `wikiname+index@host` or `wikiname+todo+comment_by_mail@host`.
13 > The basic transformation would be to call `titlepage($page)` (in the
14 > C locale), followed by replacing "/" with "+" (since "/" is not
15 > valid in mails). --[[Joey]]
16 >> I guess you are right, there is no point being more obscure
17 >> than necessary. I am leaning towards [something](http://www.cs.unb.ca/~bremner/blog/posts/encoding) not
18 >> calling titlepage but in the same spirit. --[[DavidBremner]]
20 * on the mail receiving end, these messages are either deleted, or ran through
21 a filter to be turned into blog posts.
23 - I'm thinking about how the filter should work. Within a
24 mail client, or as a batch tool to scan a mailbox? How to interact with version control, if at all?
26 * the same plugin can check for comments on a particular page next time the wiki
27 is generated, and add a link. (more or less done)
28 > If the filter just checks in the posts into revision control, the
29 > post-commit hook would handle updating the wiki to include those
30 > posts as they come in. --[[Joey]]
31 * work in progress can be
33 - [cloned](http://pivot.cs.unb.ca/git/ikiperl.git), or
34 - [browsed](http://pivot.cs.unb.ca/git/?p=ikipostal.git;a=summary)
37 Any comments? Write them here or send them to [[DavidBremner]]
39 > I don't want to derail this with too much blue-skying, but I was thinking
40 > earlier that it would be nice if ikiwiki could do something sensible with
41 > mailbox files, such as turning them into a (threaded?) blog display.
43 > One reason I was thinking about that was just that it would be nice to
44 > be able to use ikiwiki for mailing list archives. But another reason was
45 > that it would be nice to solve the problem described in
46 > [[discussion_page_as_blog]]. For that you really want a threaded system,
47 > and mailbox file formats already have threading.
49 > If that were done, it would tie into what you're working on in an
50 > interesting way, since the incoming mail would only need to be committed to
51 > the appropriate mailbox file, with ikiwiki then running to process it.
53 >> It is an interesting idea. I like that it uses an arbitrary MUA
54 >> as a "moderation" interface. One thing it made me think about is
55 >> how to encode reference (threading) information. One can of
56 >> course encode this into local-part, but I wonder if it would be
57 >> better to use header features of mailto (this could also be an
58 >> alternative to tagged mail addresses for page references).
59 >> Various client handling of mailto always seemed a bit fragile to
60 >> me but maybe I am just behind the times. Most headers are ignored, but
61 >> pseudo-headers in the body might work. For example:
62 >>[test](mailto:bremner@somewhere.ca?body=X-Iki-Page:%20test%0AX-Iki-thread:%20foobar). I hesitate to use the subject because every mail admin in the
63 >> world seems to want to add things to the front of it.
64 >> -- [[DavidBremner]]
65 >>> Although it is in python, just from reading the Debian ITP, it
67 >>> [mnemosyne-blog](http://www.red-bean.com/~decklin/mnemosyne/)
68 >>> might be an interesting backend to use or at least steal ideas
69 >>> from :-) --[[DavidBremner]]