SpamAssassin has used re2c (via sa-compile) for many years, now,
and it seems to work fine, there. GMime also looks promising
when combined with Inline::C since GMime can operate on mmap-ed
regions.
Given the inevitable demise of many .orgs when price rise;
supporting a URL rewriter similar to .mailmap makes sense.
And HTTP CONNECT seems like something our -httpd can support
to let firewalled users read over NNTP.
* general performance improvements, but without relying on
XS or pre-built modules any more than we currently do.
* 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
* 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.
* 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.
yet storing large amounts of data on computers without a
public IP behind a home Internet connection.
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.
* DHT (distributed hash table) for mapping Message-IDs to various
archive locations to avoid SPOF.
* linkify thread skeletons better
https://public-inbox.org/git/6E3699DEA672430CAEA6DEFEDE6918F4@PhilipOakley/
* linkify thread skeletons better
https://public-inbox.org/git/6E3699DEA672430CAEA6DEFEDE6918F4@PhilipOakley/
-* streaming Email::MIME replacement: currently we generate many
+* low-memory Email::MIME replacement: currently we generate many
allocations/strings for headers we never look at and slurp
allocations/strings for headers we never look at and slurp
- entire message bodies into memory.
- (this is pie-in-the-sky territory...)
+ entire message bodies into memory. GMime+Inline::C could work.
* use REQUEST_URI properly for CGI / mod_perl2 compatibility
with Message-IDs which include '%' (done?)
* use REQUEST_URI properly for CGI / mod_perl2 compatibility
with Message-IDs which include '%' (done?)