+(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 pre-built modules any more than we currently do.
+ (Optional Inline::C and user-compiled re2c acceptable)
+
+* mailmap support (same as git) for remapping expired email addresses
+
+* support remapping of expired URLs similar to mailmap
+ (coordinate with git.git with this?)
+
+* POP3 server, since some webmail providers support external POP3:
+ https://public-inbox.org/meta/20160411034104.GA7817@dcvr.yhbt.net/
+ 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 git repositories.
+
+* HTTP, IMAP and NNTP proxy support. Allow us to be a frontend for
+ firewalled off (or Tor-exclusive) instances. The use case is
+ for offering a publicly accessible IP with a cheap VPS,
+ yet storing large amounts of data on computers without a
+ public IP behind a home Internet connection.
+
+* support HTTP(S) CONNECT proxying to NNTP for users with
+ firewall problems
+
+* DHT (distributed hash table) for mapping Message-IDs to various
+ archive locations to avoid SPOF.
+
+* optional Cache::FastMmap support so production deployments won't
+ need Varnish (Varnish doesn't protect NNTP or IMAP, either)
+
+* dogfood and take advantage of new kernel APIs (while maintaining
+ portability to older Linux, free BSDs and maybe Hurd).
+
+* dogfood latest Xapian, Perl5, SQLite, git and various modules to
+ ensure things continue working as they should (or more better)
+ while retaining compatibility with old versions.
+
+* Support more of RFC 3977 (NNTP)
+ Is there anything left for read-only support?
+
+* Combined "super server" for NNTP/HTTP/POP3/IMAP to reduce memory,
+ process, and FD overhead
+
+* Configurable linkification for per-inbox shorthands:
+ "$gmane/123456" could be configured to expand to the
+ appropriate link pointing to the gmane.io list archives,
+ likewise "[Bug #123456]" could be configured to expand to
+ point to some project's bug tracker at http://example.com/bug/123456
+
+* configurable synonym and spelling support in Xapian
+
+* 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 (done for v2, doable for v1)
+
+* handle broken double-bracketed References properly (maybe)
+ and totally broken Message-IDs
+
+ cf. https://public-inbox.org/git/20160814012706.GA18784@starla/
+
+* improve documentation
+
+* linkify thread skeletons better
+ https://public-inbox.org/git/6E3699DEA672430CAEA6DEFEDE6918F4@PhilipOakley/
+
+* Further lower mail parser memory usage. We still slurp entire
+ message bodies into memory and incur 2-3x overhead on
+ multipart messages. Inline::C (and maybe gmime) could work.
+