TODO items for public-inbox

(Not in any particular order, and
performance, ease-of-setup, installation, maintainability, etc
all need to be considered for everything we introduce)

* general performance improvements, but without relying on
  XS or compiled code any more than we currently do.

* mailmap support (same as git) for remapping expired email addresses

* POP3 server, since some webmail providers support external POP3:
  Perhaps make this depend solely the NNTP server and work as a proxy.
  Meaning users can run this without needing a full copy of the
  archives in a git repository.

* HTTP and NNTP proxy support.  Allow us to be a frontend for
  firewalled off (or Tor-exclusive) instances.  The use case is
  for offering a publically accessible IP with a cheap VPS,
  yet storing large amounts of data on computers without a
  public IP behind a home Internet connection.

* TLS support for various daemons (including STARTTLS for NNTP and POP3)

* NNTP COMPRESS extension (see innd)

* Combined "super server" for NNTP/HTTP/POP3 to reduce memory overhead

* Optional reply-to-list support for mirroring lists that want it :<
  Reply-to-list encourages the existing list as a single-point-of-failure,
  but having an extra mirror using public-inbox code is nice regardless.

* Optional reply-to-nobody for dead lists.

* Configurable linkification for per-inbox shorthands:
  "$gmane/123456" could be configured to expand to the
  appropriate link pointing to the list archives,
  likewise "[Bug #123456]" could be configured to expand to
  point to some project's bug tracker at

* Support optional "HTTPS Everywhere" for mapping old HTTP to HTTPS
  links if (and only if) the user wants to use HTTPS.  We may also
  be able to configure redirects for expired URLs.

  Note: message bodies rendered as HTML themselves must NOT change,
  the links should point to an anchor tag within the same page,
  instead; giving the user options.

* configurable constants (index limits, search results)

* handle messages with multiple Message-IDs (how?)

* handle broken double-bracketed References properly (maybe)
  and totally broken Message-IDs


* portability to FreeBSD (and other Free Software *BSDs)
  (IO::KQueue is broken with Danga::Socket)

* improve documentation

* linkify thread skeletons better

* generate sample CSS for use with Stylish/dillo/etc

* streaming Email::MIME replacement: currently we generate many
  allocations/strings for headers we never look at and slurp
  entire message bodies into memory.
  (this is pie-in-the-sky territory...)

* use REQUEST_URI properly for CGI / mod_perl2 compatibility
  with Message-IDs which include '%' (done?)

* more and better test cases (use git fast-import to speed up creation)

* large mbox/Maildir/MH/NNTP spool import (see PublicInbox::Import)

* Read-only WebDAV interface to the git repo so it can be mounted
  via davfs2 or fusedav to avoid full clones.

* Improve tree layout to help giant archives (v2 format):

  * Must be optional; old ssoma users may continue using v1

  * Xapian becomes becomes a requirement when using v2; they
    claim good scalability:

  * Allow git to perform better deltafication for quoted messages

  * Changing tree layout for deltafication means we need to handle
    deletes for spam differently than we do now.

  * Deal with duplicate Message-IDs (web UI, at least, not sure about NNTP)

  * (Maybe) SQLite alternatives (MySQL/MariaDB/Pg) for NNTP article
    number mapping:

  * Ref rotation (splitting heads by YYYY or YYYY-MM)

  * Support multiple git repos for a single archive?
    This seems gross, but splitting large packs in in git conflicts
    with bitmaps and we want to use both features.  Perhaps this
    limitation can be fixed in git instead of merely being documented:

  * Optional history squashing to reduce commit and intermediate
    tree objects