unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: archive links broken with obfuscate=true
Date: Sat, 10 Apr 2021 00:06:29 -0400	[thread overview]
Message-ID: <87sg3ysrzu.fsf@kyleam.com> (raw)
In-Reply-To: <20210409233700.GA11190@dcvr>

Eric Wong writes:

> Have you run any performance tests?

No.  To get an idea of how to approach that, would you suggest I look at
xt/perf-msgview.t?

> I'm actually more worried about the '0' (of '{0,}') or '*' being
> combined with '?'.  I can't remember if there's a pathological
> case in that...

Ah, okay, sorry for missing that.

> The upper bound of N is a smaller concern, especially for
> non-spam messages which only have non-space tokens of reasonable
> length.
>
> Maybe changing the three existing '+' to {1,M} would be a way to
> ameliorate the problem (though I'm not sure what a good value of
> M would be, 255?).

Me neither, though I suspect 255 would be sufficient.

  reply	other threads:[~2021-04-10  4:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  2:11 archive links broken with obfuscate=true Kyle Meyer
2021-04-09 10:21 ` Eric Wong
2021-04-09 22:45   ` Kyle Meyer
2021-04-09 23:37     ` Eric Wong
2021-04-10  4:06       ` Kyle Meyer [this message]
2021-04-10  5:15         ` Eric Wong
2021-04-10 19:49           ` Kyle Meyer
2021-04-11  5:32             ` [PATCH v2] www: do not obfuscate addresses in URLs Eric Wong
2021-04-11  5:34               ` Eric Wong
2021-04-11 14:45               ` Kyle Meyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sg3ysrzu.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).