user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
2bf549fe2d97517a209ba8379fafc2ad70341eb1 blob 2319 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
 
hacking public-inbox
--------------------

Send all patches and "git request-pull"-formatted emails to our
self-hosting inbox at meta@public-inbox.org
It is archived at: https://public-inbox.org/meta/
and http://hjrcffqmbrq6wope.onion/meta/ (using Tor)

Contributions are email-driven, just like contributing to git
itself or the Linux kernel; however anonymous and pseudonymous
contributions will always be welcome.

Please consider our goals in mind:

	Decentralization, Accessibility, Compatibility, Performance

These goals apply to everyone: users viewing over the web or NNTP,
sysadmins running public-inbox, and other hackers working public-inbox.

We will reject any feature which advocates or contributes to any
particular instance of a public-inbox becoming a single point of failure.
Things we've considered but rejected include:

* exposing article serial numbers outside of NNTP
* allowing readers to inject metadata (e.g. votes)

We care about being accessible to folks with vision problems and/or
lack the computing resources to view so-called "modern" websites.
This includes folks on slow connections and ancient browsers which
may be too difficult to upgrade due to resource demands.

Only depend on Free Software packages which exist in the "main"
section of Debian "stable" distribution.  That is Debian 9.x
("stretch") as of this writing, but "oldstable" (8.x, "jessie")
remains supported for v1 repositories.

In general, we favor mature and well-tested old things rather than
the shiny new.

Avoid relying on compiled modules too much.  Even if it is Free,
compiled code makes packages more expensive to audit, build,
distribute and verify.  public-inbox itself will only be implemented
in scripting languages (currently Perl 5).

Performance should be reasonably good for server administrators, too,
and we will sacrifice features to achieve predictable performance.
Encouraging folks to self-host will be easier with lower hardware
requirements.

See design_www.txt and design_notes.txt in the Documentation/
directory for design decisions made during development.

For now, one may optionally subscribe to the mailing list by
sending an email to: meta+subscribe@public-inbox.org
(and confirming).  However, reading over the mailing list is
the least reliable method of reading a public-inbox.
debug log:

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

Code repositories for project(s) associated with this 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).