From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] TODO: several updates
Date: Tue, 7 Feb 2017 22:47:26 +0000 [thread overview]
Message-ID: <20170207224726.14468-1-e@80x24.org> (raw)
Always plenty to do while working on this...
---
TODO | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/TODO b/TODO
index b85887a..3163b8a 100644
--- a/TODO
+++ b/TODO
@@ -11,15 +11,28 @@ all need to be considered for everything we introduce)
* 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 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 gmane.org list archives,
@@ -36,7 +49,7 @@ all need to be considered for everything we introduce)
* configurable constants (index limits, search results)
-* handle messages with multiple Message-IDs
+* handle messages with multiple Message-IDs (how?)
* handle broken double-bracketed References properly (maybe)
and totally broken Message-IDs
--
EW
reply other threads:[~2017-02-07 22:47 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: http://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=20170207224726.14468-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).