doc: design_notes: updates for "newer" things

public-inbox-imapd, public-inbox-watch, and marketing.txt all
exist, now.

diff --git a/Documentation/design_notes.txt b/Documentation/design_notes.txt
index 71f6b77a6a8db89b0b4ea0864cb92b0b8fb85c93..3df5af3e3cf204c7954830d22a0de8b7fbd1d5e1 100644 (file)
--- 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 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
 
 * 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
 * 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
 
 * 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?
 -----------
 
 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.
 
 * 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
 -----------------
 
 Scalability notes
 -----------------
 


@@ -151,5 +154,5 @@ problems solved.
 Copyright
 ---------
 
 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>
 License: AGPL-3.0+ <http://www.gnu.org/licenses/agpl-3.0.txt>