From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] doc: design_notes: updates for "newer" things
Date: Thu, 4 Nov 2021 03:40:33 +0000 [thread overview]
Message-ID: <20211104034033.15625-1-e@80x24.org> (raw)
public-inbox-imapd, public-inbox-watch, and marketing.txt all
exist, now.
---
Documentation/design_notes.txt | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/Documentation/design_notes.txt b/Documentation/design_notes.txt
index 71f6b77a..3df5af3e 100644
--- a/Documentation/design_notes.txt
+++ b/Documentation/design_notes.txt
@@ -18,7 +18,7 @@ Use existing infrastructure
* public-inbox can coexist with existing mailing lists, any subscriber
to the existing mailing list can begin delivering messages to
- public-inbox-mda(1)
+ public-inbox-mda(1) or public-inbox-watch(1)
* public-inbox uses SMTP for posting. Posting a message to a public-inbox
instance is no different than sending a message to any _open_ mailing
@@ -72,11 +72,12 @@ Why git?
* git is distributed and robust while being both fast and
space-efficient with text data. NNTP was considered, but does not
support delta-compression and places no guarantees on data/transport
- integrity. However, a read-only NNTP gateway is implemented.
+ integrity. However, read-only IMAP and NNTP gateways are implemented.
* As of 2016, git is widely used and known to nearly all Free Software
developers. For non-developers it is packaged for all major GNU/Linux
- and *BSD distributions. NNTP is not as widely-used nowadays.
+ and *BSD distributions. NNTP is not as widely-used nowadays, and
+ most IMAP clients do not have good support for read-only mailboxes.
Why perl 5?
-----------
@@ -142,6 +143,8 @@ What sucks about public-inbox
* some (mostly GUI) mail clients cannot set In-Reply-To headers
properly without the original message.
+* marketing - as it should: <https://public-inbox.org/marketing.txt>
+
Scalability notes
-----------------
@@ -151,5 +154,5 @@ problems solved.
Copyright
---------
-Copyright 2013-2021 all contributors <meta@public-inbox.org>
+Copyright all contributors <meta@public-inbox.org>
License: AGPL-3.0+ <http://www.gnu.org/licenses/agpl-3.0.txt>
reply other threads:[~2021-11-04 3:40 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=20211104034033.15625-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).