From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] TODO: updates for done items
Date: Fri, 9 Sep 2016 09:10:41 +0000 [thread overview]
Message-ID: <20160909091041.16369-1-e@80x24.org> (raw)
The existing string -> number date range Xapian query is good
enough, and having too much flexibility is probably bad for
caching (as well as increasing our attack surface, because
parsing queries is tricky).
Tags-as-skiplists are probably not worth the effort given
Xapian, and we may have to import old messages after-the-fact,
anyways, and message delivery for mirrors is never orderly.
Other items are all done and need to be maintained (like the
search engine docs for the mairix-compatibility features that
just got pushed out)
---
TODO | 17 +++--------------
1 file changed, 3 insertions(+), 14 deletions(-)
diff --git a/TODO b/TODO
index dfee6e5..d2efcbb 100644
--- a/TODO
+++ b/TODO
@@ -14,9 +14,6 @@ all need to be considered for everything we introduce)
* TLS support for various daemons (including STARTTLS for NNTP and POP3)
-* Unix socket support for HTTP and POP3 server for use behind reverse
- proxies like nginx
-
* Combined "super server" for NNTP/HTTP/POP3 to reduce memory overhead
* Optional reply-to-list support for mirroring lists that want it :<
@@ -41,12 +38,6 @@ all need to be considered for everything we introduce)
* configurable constants (index limits, search results)
-* use tags as date-based skiplists for navigating history
- (maybe not needed with Xapian support nowadays?)
-
-* handle Xapian date range queries:
- http://mid.gmane.org/20151005222157.GE5880@survex.com
-
* handle messages with multiple Message-IDs
* handle broken double-bracketed References properly (maybe)
@@ -57,15 +48,13 @@ all need to be considered for everything we introduce)
* portability to FreeBSD (and other Free Software *BSDs)
ugh... https://rt.cpan.org/Ticket/Display.html?id=116615
-* documentation (pod/text)
+* improve documentation
* linkify thread skeletons better
https://public-inbox.org/git/6E3699DEA672430CAEA6DEFEDE6918F4@PhilipOakley/
* generate sample CSS for use with Stylish/dillo/etc
-* builtin-help for search engine syntax
-
* streaming Email::MIME replacement: currently we generate many
allocations/strings for headers we never look at and slurp
entire message bodies into memory.
@@ -74,6 +63,6 @@ all need to be considered for everything we introduce)
* use REQUEST_URI properly for CGI / mod_perl2 compatibility
with Message-IDs which include '%' (done?)
-* more test cases (use git fast-import to speed up creation)
+* more and better test cases (use git fast-import to speed up creation)
-* large mbox/Maildir/MH/NNTP spool import (use git fast-import)
+* large mbox/Maildir/MH/NNTP spool import (see PublicInbox::Import)
--
EW
reply other threads:[~2016-09-09 9:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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: http://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=20160909091041.16369-1-e@80x24.org \
--to=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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).