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-blog~I_hate_markdown@host.fqdn.tld). (DONE)
10 [more details](http://www.cs.unb.ca/~bremner/blog/posts/encoding)
12 * on the mail receiving end, these messages are either deleted, or ran through
13 a filter to be turned into blog posts.
15 - I'm thinking about how the filter should work. Within a
16 mail client, or as a batch tool to scan a mailbox? How to interact with version control, if at all?
18 * the same plugin can check for comments on a particular page next time the wiki
19 is generated, and add a link. (more or less done)
20 > If the filter just checks in the posts into revision control, the
21 > post-commit hook would handle updating the wiki to include those
22 > posts as they come in. --[[Joey]]
23 * work in progress can be
25 - [cloned](http://pivot.cs.unb.ca/git/ikiperl.git), or
26 - [browsed](http://pivot.cs.unb.ca/git/?p=ikipostal.git;a=summary)
29 Any comments? Write them here or send them to [[DavidBremner]]
31 > I don't want to derail this with too much blue-skying, but I was thinking
32 > earlier that it would be nice if ikiwiki could do something sensible with
33 > mailbox files, such as turning them into a (threaded?) blog display.
35 > One reason I was thinking about that was just that it would be nice to
36 > be able to use ikiwiki for mailing list archives. But another reason was
37 > that it would be nice to solve the problem described in
38 > [[discussion_page_as_blog]]. For that you really want a threaded system,
39 > and mailbox file formats already have threading.
41 > If that were done, it would tie into what you're working on in an
42 > interesting way, since the incoming mail would only need to be committed to
43 > the appropriate mailbox file, with ikiwiki then running to process it.
45 >> It is an interesting idea. I like that it uses an arbitrary MUA
46 >> as a "moderation" interface. One thing it made me think about is
47 >> how to encode reference (threading) information. One can of
48 >> course encode this into local-part, but I wonder if it would be
49 >> better to use header features of mailto (this could also be an
50 >> alternative to tagged mail addresses for page references).
51 >> Various client handling of mailto always seemed a bit fragile to
52 >> me but maybe I am just behind the times. Most headers are ignored, but
53 >> pseudo-headers in the body might work. For example:
54 >>[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
55 >> world seems to want to add things to the front of it.
56 >> -- [[DavidBremner]]
57 >>> Although it is in python, just from reading the Debian ITP, it
59 >>> [mnemosyne-blog](http://www.red-bean.com/~decklin/mnemosyne/)
60 >>> might be an interesting backend to use or at least steal ideas
61 >>> from :-) --[[DavidBremner]]