user/dev discussion of public-inbox itself
 help / color / Atom feed
From: Eric Wong <>
Subject: [PATCH] TODO: updates for done items
Date: Fri,  9 Sep 2016 09:10:41 +0000
Message-ID: <> (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:
 * 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)
-* documentation (pod/text)
+* improve documentation
 * linkify thread skeletons better
 * 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)

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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:

  List information:

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

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone public-inbox