X-Git-Url: http://www.git.stargrave.org/?p=public-inbox.git;a=blobdiff_plain;f=TODO;h=7a27fdd2f716e80d1542c94a00662e42c5b90ba3;hp=43eee0638f658aa1ce752b474461ba910c3fc53f;hb=HEAD;hpb=d0079a334fe2b769e4f81d6bd3c7e4346a8fa2b2 diff --git a/TODO b/TODO index 43eee063..1537179e 100644 --- a/TODO +++ b/TODO @@ -13,19 +13,13 @@ all need to be considered for everything we introduce) * 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 +* HTTP, IMAP, NNTP, POP3 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 +* support HTTP(S) CONNECT proxying to IMAP/NNTP/POP3 for users with firewall problems * DHT (distributed hash table) for mapping Message-IDs to various @@ -44,9 +38,6 @@ all need to be considered for everything we introduce) * 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, @@ -120,6 +111,13 @@ all need to be considered for everything we introduce) * improve performance and avoid head-of-line blocking on slow storage (done for most git blob retrievals, Xapian needs work) +* allow optional use of separate Xapian worker process to implement + timeouts and avoid head-of-line blocking problems. Consider + just-ahead-of-time builds to take advantage of custom date parsers + (approxidate) and other features not available to Perl bindings. + +* integrate git approxidate parsing into Xapian w/o spawning git + * HTTP(S) search API (likely JMAP, but GraphQL could be an option) It should support git-specific prefixes (dfpre:, dfpost:, dfn:, etc) as extensions. If JMAP, it should have HTTP(S) analogues to @@ -153,8 +151,10 @@ all need to be considered for everything we introduce) * support UUCP addresses for legacy archives -* decode (skip indexing of) base-85 binary patches to avoid false-positives - * support pipelining as an IMAP/NNTP client for -watch + lei -* auto-detect and reload on TLS cert+key changes in daemons +* expose lei contents via read/write IMAP/JMAP server for personal use + +* git SHA-256 migration/coexistence path + +* decode RFC 3676 format=flowed + DelSp properly (see mflow (mblaze), mutt, ...)