X-Git-Url: http://www.git.stargrave.org/?a=blobdiff_plain;f=README;h=ae428bcfe11796657c97913dabdf45b5a2bc9fd2;hb=78e81ae914ad24dfdbce8f7fb98d4c8979743c77;hp=7618727a93ea67ea2f202ef4347c14cb756223bf;hpb=120b17a46f06e143d4a59825cdd5db72e852cff2;p=public-inbox.git
diff --git a/README b/README
index 7618727a..ae428bcf 100644
--- a/README
+++ b/README
@@ -14,7 +14,8 @@ public-inbox spawned around three main ideas:
use of non-Free services or software.
* Graphical user interfaces should not be required for text-based
- communication.
+ communication. Users may have broken graphics drivers, limited
+ eyesight, or be unable to afford modern hardware.
public-inbox aims to be easy-to-deploy and manage; encouraging projects
to run their own instances with minimal overhead.
@@ -22,8 +23,9 @@ to run their own instances with minimal overhead.
Implementation
--------------
-public-inbox stores mail in a git repository keyed by Message-ID
-as documented in: https://ssoma.public-inbox.org/ssoma_repository.txt
+public-inbox stores mail in git repositories as documented
+in https://public-inbox.org/public-inbox-v2-format.txt and
+https://public-inbox.org/public-inbox-v1-format.txt
By storing (and optionally) exposing an inbox via git, it is
fast and efficient to host and mirror public-inboxes.
@@ -35,10 +37,10 @@ discussions if archives do not expose Message-ID and References
headers. List server admins are also burdened with delivery
failures.
-public-inbox uses the "pull" model. Casual readers may also
+public-inbox uses the "pull" model. Casual readers may
follow the list via NNTP, Atom feed or HTML archives.
-If a reader loses interest, they simply stop syncing.
+If a reader loses interest, they simply stop following.
Since we use git, mirrors are easy-to-setup, and lists are
easy-to-relocate to different mail addresses without losing
@@ -75,6 +77,9 @@ Requirements (participant)
their mailers to reduce the impact of a public-inbox as a
single point of failure.
+* The HTTP web interface exposes mboxrd files, and NNTP clients often
+ feature reply-by-email functionality
+
* participants do not need to install public-inbox, only server admins
Requirements (server)
@@ -85,9 +90,11 @@ See https://public-inbox.org/INSTALL
Hacking
-------
-Source code is available via git:
+AGPL source code is available via git:
- git clone https://public-inbox.org/ public-inbox
+ git clone https://public-inbox.org/public-inbox.git
+ git clone https://repo.or.cz/public-inbox.git
+ torsocks git clone http://hjrcffqmbrq6wope.onion/public-inbox
See below for contact info.
@@ -119,10 +126,7 @@ And as Tor hidden services:
You may also clone all messages via git:
git clone --mirror https://public-inbox.org/meta/
-
-Or pass the same git repository URL for ssoma using the instructions at:
-
- https://ssoma.public-inbox.org/README.html
+ torsocks git clone --mirror http://hjrcffqmbrq6wope.onion/meta/
Anti-Spam
---------
@@ -137,7 +141,7 @@ Content Filtering
-----------------
To discourage phishing, trackers, exploits and other nuisances,
-only plain-text emails are allowed and HTML is rejected.
+only plain-text emails are allowed and HTML is rejected by default.
This improves accessibility, and saves bandwidth and storage
as mail is archived forever.
@@ -148,7 +152,7 @@ aims to preserve the focus on content, and not presentation.
Copyright
---------
-Copyright 2013-2016 all contributors
+Copyright 2013-2020 all contributors
License: AGPL-3.0+
This program is free software: you can redistribute it and/or modify