<blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Those are definitely valid concerns. Has anyone made a wiki-like site with <br>Yesod? I hadn't heard of Yesod until I joined this mailing list, but I've <br>seen quite a bit of buzz around it since then. If a large enough chunk of <br>
the community is backing a framework and focusing on making it secure and <br>reliable, then it should be possible to build applications with it (wikis, <br>blogs, etc.) that draw on the framework's strength and security. You may <br>
still have security issues, but if they're continually addressed and <br>maintained at the framework level it benefits everyone building applications <br>on top of that framework. I'm still relatively new to the Haskell community <br>
so I apologize if much of this has been addressed before! </blockquote><div><br></div><div>It is dead-simple to deploy a fast haskell web app, so haskell *might* have a chance at solving the problem, but likely it can be fixed much faster by doing a better job configuring the server or adding more resources.</div>
<div><br></div><div>I think that security issues are a bit of a red herring. You can go through potential security issues one-by-one and basically make them impossible in a web/wiki framework (as we are doing in Yesod). Of course this is easier to do with a type system in Haskell. And of course some security is outside the scope of the software and needs to be established by procedure (admin server access should only be through ssh key, etc).</div>
<div>Gitit uses darcs or git to store data, but through the command line interfaces. Unfortunately to my knowledge darcs does not expose a library interface. Gitit could be made faster and more secure by interfacing with libgit2.</div>
<div>Even though it is may not be socially acceptable to state it, it is likely that gitit or any haskell library would be more secure in practice because it is more obscure. And the kind of security we really care about in the wiki- the wiki page content- can be easily replicated and restored.</div>
<div><br></div><div>I definitely agree that the hard and boring part of switching to a haskell wiki is converting existing MediaWiki content and configuration to a new system- that would have to be investigated first.</div>
<div><br></div><div>Unfortunately this is probably all bike-shedding and my original question of how can the community speed up the wiki hasn't been answered :)</div><div><br></div><div>Greg Weber</div>