Date | Commit message (Collapse) |
|
|
|
Just in case there is an error, this should be more explicit.
|
|
This shaves off nearly 100ms when my Core2Duo is clocked to 800Mhz
when rendering a full HTML index.
|
|
Git::cat_blob is a handy interface to read multiple emails
without incurring fork + exec overhead. Git.pm is GPLv2+,
not GPLv2-only, so we may link to it.
|
|
We need -learn to do many of the same things as -mda
when we have a false-positive. We also need -learn to
do HTML filtering in case the training user screws up.
|
|
We will be combining common code between -learn and -mda
|
|
We have an HTML homepage, OMG!
|
|
The emergency destination may be Maildir. A Maildir emergency
destination is better for volatile data which is written to
and deleted-from frequently.
|
|
This allows WWW readers to slowly page through the entire history
of the mailing list.
|
|
The lack of trailing whitespace in quote prefixes threw us
off and cause t/view to fail.
This failure was caused by
commit fefea3d7d2484ffbf433aec0dd80026aa7120e07
("ensure per-message short quotes do not get too long")
and not caught before pushing because I failed to run
"make", only "prove" (and not even "prove -l" :x).
|
|
Sometimes a single long word or URL can lengthen the line
too much.
|
|
This is hopefully the most user-friendly method.
|
|
It is pointless to link to ourselves.
|
|
We need to take care to escape everything properly to avoid
HTML/JS injections.
|
|
Some people like old-fashioned Ruby and WEBrick is in the Ruby
standard library, so widely available.
|
|
Breaking up short quote messages at 1 line is too disconcerting,
try 5 lines as proper quotes shouldn't be too long.
|
|
This may be easier in some cases for copy+paste, but not 100%
reliable in case the .txt and .html suffixes are in the Message-ID
itself.
|
|
This makes it slightly easier for out-of-the-box curl users since
curl does not report or show the error by default.
|
|
|
|
This affects users of long-lived processes (FastCGI/Plack)
|
|
CGI mounts should probably handle this internally. We're reverting
this since it adds too much potential for abuse with fake/extra
prefixes in the URL. We also need to reorder our redirect handling
as a result.
This reverts commit c394de9f2c91c2c5ed1f7832a5a7cc0206120b7f.
|
|
Lightly tested, but this seems to work OK.
|
|
|
|
Maybe this increases readability for now.
|
|
Long URLs are not needed for HTML pages, but may be for feeds since
they're often resyndicated and not consumed by the browser.
|
|
We may be breaking some parsers or allowing more breakage
to slip through without quotes. We waste some bytes, though.
|
|
Users with non-US-ASCII compatible names were not showing
up properly in "git log" output.
|
|
Unfortunately, this means we get rid of parallelization,
as we need to preserve delivery order so HTML indices look
chronological. Order may also affect spam filtering and
training, too.
|
|
Fortunately, most mailing lists will never grow too large.
|
|
Hopefully this makes the scope and intent of the project clearer.
|
|
"bugs" might confuse and limit the discussion, so "meta" it is!
|
|
These probably make sense even though we do not handle
delivery ourselves. It can aid in searching/filtering/tagging
of messages.
|
|
This may be useful for generating List-Id headers and HTML pages.
|
|
We do not have all messages in the top-level index
(and we need to adjust the test while we're at it).
|
|
It is common to type upper-level URLs without the slash,
redirect users to the correct page for usability.
|
|
Not sure what I was thinking...
|
|
MIDs may have strange characters in them, so we need to handle
escaping/unescaping properly to avoid broken links or worse.
|
|
This might make it easier to go to non-CGI things.
|
|
We may have something like /foo.cgi/m/$MID.html in there.
|
|
This makes it easier to configure for systems which
determine a script is a CGI script based on suffix.
|
|
We may promote this to be a real script, since public-inbox-mda
is idempotent.
|
|
Message-IDs could have embedded '<' and '>'
|
|
This makes it possible to gradually migrate to new address in case
of list name changes, and is one step closer to operating in
"stealth hijack mode" :)
|
|
This is essential for integrating into my inotify-based
spam training setup.
|
|
Laziness \o/
(Then impatience and hubris :)
|
|
I often forget the subtleties of Perl regexps and newlines,
so I suspect others do, too. Use explicit capture so it's
more familiar to users of non-Perl regexps.
|
|
These need better tests and verification, but it's something
for now.
|
|
Code should be consistent with the design docs
(and we will need better tests).
|
|
Hopefully it's slightly easier-to-follow this way.
|
|
This prevents ambiguity when switching URLs between static
file servers and CGI.
The /$LISTNAME/index.html URL appearing in the wild is inevitable
because of our static file server support. Worst yet, there's
no easy/consistent way to get all installations detect and 301
them to the shorter /$LISTNAME/. So we make the CGI support
/$LISTNAME/index.html.
The downside of this is the potential duplicate entry in all caches.
|