From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jason at zx2c4.com (Jason A. Donenfeld)
Date: Mon, 12 Oct 2015 14:12:22 +0200
Subject: filter rework break about page
In-Reply-To: <20151012130514.2a10b373@leda.localdomain>
References: <20151011120620.0f83f58c@leda.localdomain>
 <20151011120834.5a1e1fff@leda.localdomain>
 <20151011122841.7dd369e2@leda.localdomain>
 <CAHmME9o9-gpQQV0b8OnCkCu8Z4htdRnDpiCCRqRBUQseNZ+R8Q@mail.gmail.com>
 <20151011181315.2b7208aa@leda.localdomain>
 <20151012115721.7c2d3b7d@leda.localdomain>
 <20151012130514.2a10b373@leda.localdomain>
Message-ID: <CAHmME9qYXNn-mLatdSXdFUWmriRT4mmcUa4VCZ4_iFpEs6oXcw@mail.gmail.com>

On Mon, Oct 12, 2015 at 1:05 PM, Christian Hesse <list at eworm.de> wrote:
>> [0] http://www.pell.portland.or.us/~orc/Code/discount/
>
> BTW, this brings a shared library libmarkdown.so. We could link cgit against
> that and handle markdown without external command.

Definitely not. In the first case, I wouldn't want to special case
this. Though, I wouldn't mind adding support for *yet another filter
type* - dlopen. Nonetheless, Lua serves the highspeed case rather
well. But in fact my real concern is that different sites have wildly
differing requirements on what kind of markdown they output. Github
flavored? Italics within words? Should it filter out dangerous HTML?
Etc. Too many decisions, that are best off to a tweakable script.