Re: Broken linkparsing in archives

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: Broken linkparsing in archives
Date: 2022-11-03 13:17:43
Message-ID: CABUevEyu4tT7Eqe7Ph8enZ9VDU1V1M1i+0m6pN1cdv0Too5hSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Wed, Nov 2, 2022 at 1:52 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:

> > On 2 Nov 2022, at 13:39, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> > And I'm not sure they *should* be considered, since the mime type of the
> body isn't markdown...
>
> For emails sent as text to -announce, sure. But. Since we support
> markdown
> formatting in news postings that go out to -announce, it seems a bit
> unhelpful
> to generate broken links for all those posts.
>

I agree with the principe, but the question is how reliable we can make it.
(One oculd also argue we *should* post those as text/markdown, but I fear
that will break even more MUAs).

If I can come up with a filter that converts a broken link from urlize for
> the
> known case of markdown links, would that be an accepted solution?
>

If it can be made reliable, I think that would be acceptable. It needs to
be validated that it works in the full chain that we use on the site (we
also include the silly obfuscation of email addresses in the filter chain),
but as long as that's done I think we can and should do it.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Dave Page 2022-11-03 14:19:44 Re: Dark mode styling for the website
Previous Message Daniel Gustafsson 2022-11-02 12:52:40 Re: Broken linkparsing in archives