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.
+ XS or pre-built modules any more than we currently do.
* mailmap support (same as git) for remapping expired email addresses
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)
+* optional Cache::FastMmap support so production deployments won't
+ need Varnish (Varnish doesn't protect NNTP, either)
-* NNTP COMPRESS extension (see innd)
+* dogfood and take advantage of new kernel APIs (while maintaining
+ portability to older Linux, free BSDs and maybe Hurd).
-* Combined "super server" for NNTP/HTTP/POP3 to reduce memory overhead
+* 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.
-* 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.
+* Support more of RFC 3977 (NNTP)
-* Optional reply-to-nobody for dead lists.
+* Combined "super server" for NNTP/HTTP/POP3 to reduce memory overhead
* Configurable linkification for per-inbox shorthands:
"$gmane/123456" could be configured to expand to the
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.
* configurable constants (index limits, search results)
-* handle messages with multiple Message-IDs (how?)
+* 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/
-* portability to FreeBSD (and other Free Software *BSDs)
- ugh... https://rt.cpan.org/Ticket/Display.html?id=116615
- (IO::KQueue is broken with Danga::Socket)
-
* improve documentation
* linkify thread skeletons better
https://public-inbox.org/git/6E3699DEA672430CAEA6DEFEDE6918F4@PhilipOakley/
-* 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.
* Read-only WebDAV interface to the git repo so it can be mounted
via davfs2 or fusedav to avoid full clones.
+ davfs2 needs Range: request support for this to be feasible:
+ https://savannah.nongnu.org/bugs/?33259
+ https://savannah.nongnu.org/support/?107649
+
+* Contribute something like IMAP IDLE for "git fetch".
+ Inboxes (and any git repos) can be kept up-to-date without
+ relying on polling.
+
+* Improve bundle support in git to make it cheaper to host/clone
+ with dumb HTTP(S) servers.
+
+* Expose targeted reindexing of individual messages.
+ Sometimes an indexing bug only affects a handful of messages,
+ so it's not worth the trouble of doing a full reindex.
+
+* code repository integration (with cgit, gitweb, etc...)
-* Improve tree layout to help giant archives (v2 format):
+* migration path to v2 without breaking v1 "git fetch" cronjobs
- * Must be optional; old ssoma users may continue using v1
+* imperfect scraper importers for obfuscated list archives
+ (e.g. obfuscated Mailman stuff, Google Groups, etc...)
- * Xapian becomes becomes a requirement when using v2; they
- claim good scalability: https://xapian.org/docs/scalability.html
+* consider using HTTP::Date instead of Date::Parse, since we need the
+ former is capable of parsing RFC822-ish dates, used by Plack, and
+ the latter is missing from OpenBSD and maybe other distros.
- * Allow git to perform better deltafication for quoted messages
+* improve performance and avoid head-of-line blocking on slow storage
- * Changing tree layout for deltafication means we need to handle
- deletes for spam differently than we do now.
+* share "git cat-file --batch" processes across inboxes to avoid
+ bumping into /proc/sys/fs/pipe-user-pages-* limits
- * Deal with duplicate Message-IDs (web UI, at least, not sure about NNTP)
+* make "git cat-file --batch" detect unlinked packfiles so we don't
+ have to restart processes (very long-term)
- * (Maybe) SQLite alternatives (MySQL/MariaDB/Pg) for NNTP article
- number mapping: https://www.sqlite.org/whentouse.html
+* support searching based on `git-patch-id --stable` to improve
+ bidirectional mapping of commits <=> emails
- * Ref rotation (splitting heads by YYYY or YYYY-MM)
+* linter to check validity of config file
- * 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:
- https://public-inbox.org/git/20160428072854.GA5252@dcvr.yhbt.net/
+* linter option and WWW endpoint to graph relationships and flows
+ between inboxes, addresses maildirs, coderepos, etc...
- * Optional history squashing to reduce commit and intermediate
- tree objects
+* pygments support - via Python script similar to `git cat-file --batch'
+ to avoid startup penalty. pygments.rb (Ruby) can be inspiration, too.