user/dev discussion of public-inbox itself
 help / color / Atom feed
d2efcbb6a9fc9a3f08808f7a61fde51dc93cd35a blob 2597 bytes (raw)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
 
TODO items for public-inbox

(Not in any particular order, and
performance, ease-of-setup, installation, maintainability, etc
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.

* mailmap support (same as git) for remapping expired email addresses

* POP3 server, since some webmail providers support external POP3:
  https://public-inbox.org/meta/20160411034104.GA7817@dcvr.yhbt.net/

* TLS support for various daemons (including STARTTLS for NNTP and POP3)

* 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.

* Configurable linkification for per-inbox shorthands:
  "$gmane/123456" could be configured to expand to the
  appropriate link pointing to the gmane.org list archives,
  likewise "[Bug #123456]" could be configured to expand to
  point to some project's bug tracker at http://example.com/bug/123456

* 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.

  Note: message bodies rendered as HTML themselves must NOT change,
  the links should point to an anchor tag within the same page,
  instead; giving the user options.

* implement RFC 4685 (Atom message threading)

* configurable constants (index limits, search results)

* handle messages with multiple Message-IDs

* 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

* 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.
  (this is pie-in-the-sky territory...)

* use REQUEST_URI properly for CGI / mod_perl2 compatibility
  with Message-IDs which include '%' (done?)

* more and better test cases (use git fast-import to speed up creation)

* large mbox/Maildir/MH/NNTP spool import (see PublicInbox::Import)
debug log:

solving d2efcbb ...
found d2efcbb in https://80x24.org/public-inbox.git

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror https://public-inbox.org/meta
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.org/gmane.mail.public-inbox.general

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox