<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV> </DIV><BR><DIV><DIV>On Oct 4, 2006, at 10:32 PM, Patrick R. Michaud wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">4) I am trying to get people to jointly edit pages, not just bottom<SPAN class="Apple-converted-space"> </SPAN></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">post to a page - for that I could use a bulletin board</FONT></P> </BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Comic Sans MS; min-height: 16.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">Valid point.<SPAN class="Apple-converted-space"> </SPAN>In 2004 we originally thought of the mail-to-wiki</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">gateway because there was a lot of useful information on the</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">mailing list that wasn't finding its way onto the pmwiki.org site.</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">Having the gateway would make it easy for people (especially me)</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">to just say "throw this content up there -- someone can come back</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">and reformat it later".</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>Or people can peruse their own sent-mail archives and do the same for a variety of reasons.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Say I send an announcement to one of my mailing lists -- Big Event Coming!! Mark your calendar!</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>And I want an announcement page on the wiki. I could BCC my wiki.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I don't want to require the start/end tags. That would have to be optional. Sometimes I just want the whole body of the message AND I don't want to have to go back and re-edit, or explain to other users that *I* have the magical ability to do this and haven't passed it along to them. nya!</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I see email->wiki as a limited tool, but a feature that would be great to support for those of us who would find it useful. I really DON'T think it's meant to be a public or general use tool. It would be too easy to abuse. BUT I am willing to try to make hooks for different items.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Patrick:</DIV><DIV>You can write your end of the wiki app in Perl6, what does that have to do with how the RECEIVING wiki processes the email.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>If we make one plug-in portion for any wiki that wants to receive the email info via HTTP -- it has to be php. -- or wiki code. We would send the same HTTP/POST requests to the receiving wiki(s) -- we'd only be changing the origin of the HTTP/POST and agreeing on the same formats and markup for the emails, to create a common API. You can program your email-to-external-wikis code in Perl6, I'd be developing mine in PHP, and both can use HTTP/POST requests to get the job done.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>If I can find a curl-like plug-in that doesn't require libcurl. And they probably exist.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>How were you thinking the wiki on the receiving end should behave? How would your HTTP/POST request authenticate and deliver info to the receiving wiki without an API of sorts on the other end?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Crisses</DIV></BODY></HTML>