thoughts

[git.ikiwiki.info.git] / doc / todo / comment_by_mail.mdwn

diff --git a/doc/todo/comment_by_mail.mdwn b/doc/todo/comment_by_mail.mdwn
index 50f1f89685587965890839b20967a2fa2a4a2cea..085c4896fb436d217594e38aebb8502c000d19a2 100644 (file)
--- a/doc/todo/comment_by_mail.mdwn
+++ b/doc/todo/comment_by_mail.mdwn
@@ -6,15 +6,20 @@ 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
   * 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) 
+    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
   * 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)
 
   * 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)

+    > If the filter just checks in the posts into revision control, the
+    > post-commit hook would handle updating the wiki to include those
+    > posts as they come in. --[[Joey]]

   * work in progress can be 
 
    - [cloned](http://pivot.cs.unb.ca/git/ikiperl.git), or 
   * work in progress can be 
 
    - [cloned](http://pivot.cs.unb.ca/git/ikiperl.git), or 


@@ -23,3 +28,26 @@ I have in mind something like
 
 Any comments? Write them here or send them to [[DavidBremner]]
 
 
 Any comments? Write them here or send them to [[DavidBremner]]
 

+> I don't want to derail this with too much blue-skying, but I was thinking
+> earlier that it would be nice if ikiwiki could do something sensible with
+> mailbox files, such as turning them into a (threaded?) blog display.
+> 
+> One reason I was thinking about that was just that it would be nice to 
+> be able to use ikiwiki for mailing list archives. But another reason was
+> that it would be nice to solve the problem described in
+> [[discussion_page_as_blog]]. For that you really want a threaded system,
+> and mailbox file formats already have threading.
+> 
+> If that were done, it would tie into what you're working on in an
+> interesting way, since the incoming mail would only need to be committed to
+> 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.  After I killed a debian BTS entry with 
+>> clumsy pseudoheader editing I think any 
+>> reference info should also be encoded into the address.
+>>> 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 :-)  --[[DavidBremner]]