user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] TODO: a few more updates
Date: Thu, 19 Apr 2018 19:43:59 +0000	[thread overview]
Message-ID: <20180419194359.21139-1-e@80x24.org> (raw)

Mainly, v2 stuff is done
---
 TODO | 41 ++++++++---------------------------------
 1 file changed, 8 insertions(+), 33 deletions(-)

diff --git a/TODO b/TODO
index 605013e..6b99c60 100644
--- a/TODO
+++ b/TODO
@@ -25,11 +25,9 @@ all need to be considered for everything we introduce)
 
 * NNTP COMPRESS extension (see innd)
 
-* Combined "super server" for NNTP/HTTP/POP3 to reduce memory overhead
+* Support more of RFC 3977 (NNTP)
 
-* 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.
+* Combined "super server" for NNTP/HTTP/POP3 to reduce memory overhead
 
 * Optional reply-to-nobody for dead lists.
 
@@ -49,7 +47,7 @@ all need to be considered for everything we introduce)
 
 * 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
@@ -79,33 +77,10 @@ all need to be considered for everything we introduce)
 
 * 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: https://xapian.org/docs/scalability.html
+* Optionally allow indexing Xapian without positional information to
+  save space (but prevents "quoted phrase" searching).
 
-  * Allow git to perform better deltafication for quoted messages
+* Allow NNTP and more of PSGI code to work without Xapian
 
-  * 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: https://www.sqlite.org/whentouse.html
-
-  * 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:
-    https://public-inbox.org/git/20160428072854.GA5252@dcvr.yhbt.net/
-
-  * Optional history squashing to reduce commit and intermediate
-    tree objects
+* Read-only WebDAV interface to the git repo so it can be mounted
+  via davfs2 or fusedav to avoid full clones.
-- 
EW


                 reply	other threads:[~2018-04-19 19:43 UTC|newest]

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

Reply instructions:

You may reply publicly 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20180419194359.21139-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).