X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/f0d9bf00dcdb68ed95c334c55dc06a4669c77fc7..82197bd0eaa216b841caace38c976acc7f6ad3fa:/doc/todo/comment_by_mail.mdwn?ds=inline diff --git a/doc/todo/comment_by_mail.mdwn b/doc/todo/comment_by_mail.mdwn index ed9db0621..6d3eeb044 100644 --- a/doc/todo/comment_by_mail.mdwn +++ b/doc/todo/comment_by_mail.mdwn @@ -6,22 +6,14 @@ I have in mind something like * add a mailto: url to each page matching some pagespec (currently every page gets a comment footer) * this mailto url goes to an address identifying the page (something like - user-iki-FE653b@host.fqdn.tld). (DONE) - > I wonder if it would be more or less natural to put an encoded form - > of the page name in the email address? I'm thinking about something - > like `wikiname+index@host` or `wikiname+todo+comment_by_mail@host`. - > The basic transformation would be to call `titlepage($page)` (in the - > C locale), followed by replacing "/" with "+" (since "/" is not - > valid in mails). --[[Joey]] - >> I guess you are right, there is no point being more obscure - >> than necessary. I am leaning towards [something](http://www.cs.unb.ca/~bremner/blog/posts/encoding) not - >> calling titlepage but in the same spirit. --[[DavidBremner]] - + user-iki-blog~I\_hate\_markdown@host.fqdn.tld). (DONE) + [more details](http://www.cs.unb.ca/~bremner/blog/posts/encoding) + * on the mail receiving end, these messages are either deleted, or ran through - a filter to be turned into blog posts. - - - I'm thinking about how the filter should work. Within a - mail client, or as a batch tool to scan a mailbox? How to interact with version control, if at all? + a filter to be turned into blog posts. As a first step, I have +[written](http://pivot.cs.unb.ca/git/?p=ikipostal.git;a=blob_plain;f=filters/postal-filer.pl;hb=010357a08e9) +a filter that decodes the address and writes the message into an appropriate +mailbox. I would be interested in any ideas people have about security. * the same plugin can check for comments on a particular page next time the wiki is generated, and add a link. (more or less done) @@ -51,19 +43,11 @@ Any comments? Write them here or send them to [[DavidBremner]] > the appropriate mailbox file, with ikiwiki then running to process it. > --[[Joey]] >> It is an interesting idea. I like that it uses an arbitrary MUA ->> as a "moderation" interface. One thing it made me think about is ->> how to encode reference (threading) information. One can of ->> course encode this into local-part, but I wonder if it would be ->> better to use header features of mailto (this could also be an ->> alternative to tagged mail addresses for page references). ->> Various client handling of mailto always seemed a bit fragile to ->> me but maybe I am just behind the times. Most headers are ignored, but ->> pseudo-headers in the body might work. For example: ->>[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 ->> world seems to want to add things to the front of it. ->> -- [[DavidBremner]] ->>> Although it is in python, just from reading the Debian ITP, it ->>> looks like ->>> [mnemosyne-blog](http://www.red-bean.com/~decklin/mnemosyne/) ->>> might be an interesting backend to use or at least steal ideas ->>> from :-) --[[David Bremner]] +>> as a "moderation" interface. After I killed a debian BTS entry with +>> clumsy pseudoheader editing I think any +>> reference info should also be encoded into the address. + +The current version of this plugin is now running on my home page. See for example +[a recent post in my blog](http://www.cs.unb.ca/~bremner/blog/posts/can-i-haz-a-distributed-rss/). +Unfortunately although the [[mailbox|todo/mbox]] renderer supports threading, I haven't had +a chance to implement comments on comments yet. [[DavidBremner]]