Tim’s comment challenge…

Now he mentions Rails but reading his thoughts on the design would have to agree with his conclusion that that’s overkill. For a start why inject a long list of dependencies and a steep learning curve for a relatively simple application (that applies to any framework BTW – not just Rails)? Also as he’s leaning towards files not DB so no need for ActiveRecord etc.

Anyway – strikes me the most sensible solution would be just a CGI script (probably Perl) – he plans static output – the comments are “compiled” on approval – doesn’t need to handle high load but (to reduce the pain of that admin interface) needs to be easy to hack the UI once he can see where the time goes.

Do we recommend Tim use a forms library? E.g. QuickForm or Patforms (related point – where do we point him for help installing PEAR if needed)? Against this is I doubt the comment form really requires a full forms library – vanilla PHP?

For comment markup, what to we want to point Tim at? As mentioned before, SafeHTML (packaged under PEAR as HTML_Safe) would allow posting raw HTML, perhaps with help from tidy to make sure it’s XHTML. There is PHP Markdown (don’t know much about this e.g. security record / UTF-8 handling) for a fairly standard markup. Alternatively Dokuwiki’s parser could be extracted (with a little hacking) – shouldn’t harm UTF-8 and shouldn’t result is broken XHTML. What else?

For authentication OpenID seems to be on it’s way to becoming a serious contender – it seems like Wikipedia is planning to support it some time this summer (more on that later) – there’s libraries in pretty much any common language, although can’t say how rubust the PHP stuff is.